Hi,
When I use an aggregator in my scenario, the only structure I can use is “Custom.” I have a bunch of structures defined but the aggregator doesn’t see any of them.
What am I missing?
L
1 Like
Hello @L_Duperval,
Which type of Aggregator are you using?
For Array, the Data Structure comes from a downstream module where Map is enabled.
For JSON you create your own and should be able to select it.
4 Likes
You need to map the whole array within an existing field that already has a mappable “structure”.
The below explains this phenomenon further:
Every result (item/record) from a iterator/search/match module will output a bundle. To “combine” them into a single structure, you’ll need to use an aggregator of some sort.
Aggregators are modules that accumulate multiple bundles into one single bundle. An example of a commonly-used aggregator module is the Array aggregator module. The next popular aggregator is the Text Aggregator which is very flexible and has applies to many use-cases.
There are other types of aggregator modules, click the below links to find out more:
- Array aggregator
- Text aggregator
- Numeric aggregator
- Table aggregator
- JSON aggregator
- CSV aggregator
- Archive (ZIP) aggregator
- other app-specific aggregators
Read This
The Array Aggregator module allows you to build a complex array of collections for a later module’s field to map multiple items (collections) to it.
Here is an example of using the “Target structure type” of an Array Aggregator module:
As you can see, the “Map” toggle on fields are used when you have an array. You can easily build an array variable to map to a field, by using an Array Aggregator module and select the “Target Structure Type” as the future field you want to map the array into.
samliew – request private consultation
Join the Make Fans Discord server to chat with other makers!
1 Like
Ah, that was it. The structure has to be defined/used after the Array Aggregator, and I missed that it had to be mapped downstream.
Thanks!
L