What are you trying to achieve?
Hi all,
I seem to remember in one of the earlier Make Academy modules an explanation on when to use a Text Aggregator versus the Compose a String module, but I cannot remember the difference.
Can someone please explain to me when someone would use one versus the other? It seems like both can map to data in previous modules of the scenario…
Steps taken so far
I have checked the Make Basics > Introduction to Aggregators > Text Aggregators in Action unit but it doesn’t get too deep into depth.
Welcome to the Make community!
Aggregators combine multiple bundles into a single operation. If you send in 10 bundles, out comes 1 single text bundle.
Compose a string will compose a string for each bundle, while still passing through the original number of bundles sent to it. If you send in 10 bundles, you use 10 “Compose a strings”, and 10 output bundles.
Aggregators
Every result (item/record) from 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.
There are other types of aggregator modules, click the below links to find out more:
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
P.S.: Did you know, the concepts of about 70% of questions asked on this forum are already covered in the Make Academy. Investing some effort into it will save you lots of time and frustration using Make later!
Thank you @samliew !
That makes sense in theory. Do you have any examples of use cases in practice where I would use one versus the other?