An Azure service for ingesting, preparing, and transforming data at scale.
(EDITED, FOUND A SOLUTION)
Given the sample data file (JSON):
{"foo":[1,2,3,4,5]}
we can use alternative syntax to turn it into
1
2
3
4
5
In the above picture, in the mapping I specify the collectionReference as $['foo'] and the source as foo not $['foo']. Also the type is specified in the destination.
I found the subtle difference of $[...] to be very important. When $[...] is used, this is specifying the entire path. When leaving out the $[...] it can search for anywhere in the document, including the results of cross-apply that collectionReference does.