Processing the result from an aggregator field containing multiple Operations

[krkovice]

What are you trying to achieve?

The goal is to get a simple json output from an array aggregator that contains data split into multiple operations from previous iterations.
I need to build a json string that will have the formatting of individual operations:
{
“MyID”: [
ID from json Operation 1,
ID from json Operation 2,
ID from json Operation 3,
“#end”
]
}

Steps taken so far

I have tried different json and text aggregators but I always get more operations back. I am trying to build a simple test string using the map function, but even this is then divided by operation.
I have tried setting the string to be built only after it has been built using the input filter, but it always takes the last operation.

Screenshots: scenario setup, module configuration, errors

[samliew]

Welcome to the Make community!

Setting the Correct Aggregator Source

You need to set the “Source Module” field of the aggregator to where the bundles are coming from. This is usually an iterator module, but can also be a search/list/repeater module, or even the trigger module!

For more information, please refer to the Make Academy.

Combining Bundles Using Aggregators

Every result (item/record) from trigger/iterator/list/search/match modules will output a bundle. This can result in multiple bundles, which then trigger multiple operations in future modules (one operation per bundle). To “combine” multiple bundles into a single variable, 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 can apply to many use-cases like building of JSON, CSV, HTML.

You can find out more about the other types of aggregator modules here:

• Array aggregator
• Text aggregator
• Numeric aggregator
• Table aggregator
• JSON aggregator
• CSV aggregator
• Archive (ZIP) aggregator
• other app-specific aggregators

Mapping a Specific Structure Into a Complex Field

The Array Aggregator module is very powerful because it allows you to build a complex array of collections for a later module’s field to map multiple items (collections) to it.

This is done using the “Target structure type” field in an Array Aggregator module.

Here is an example:

As you can see, the “Map” toggle on complex fields are used when you have an array. You can easily build an array variable to map to a future module’s field, by using an Array Aggregator module and select the “Target Structure Type” as the future module’s field you have mapped the array into.

Example

Here is an example of how your scenario could look:

This is just an example. Your final solution may or may not look like this depending on your requirements and actual input data.

Hope this helps! Let me know if there are any further questions or issues.

— @samliew

P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.

[krkovice]

Thank you for this, that was my problem
↓ ↓ ↓

@samliew

You need to set the “Source Module” field of the aggregator to where the bundles are coming from. This is usually an iterator module, but can also be a search/list/repeater module, or even the trigger module!

Martin