Hi Makers, I’m struggling to give this a proper title (perhaps you have a suggestion?) and instead describe what I’m looking for.
Airtable module outputs multiple bundles.
Retrieve the data storage once instead of for each bundle.
Continue processing the original bundles.
So basically go from many to one to many.
The following steps make this a fairly complex scenario and I’m reluctant to rebuilt the entire workflow by replacing the trigger module. I wonder if there’s an alternative of doing this? Thanks!
If your Airtable Search Records limit is set to something above 1 (I believe the default is 10 in advanced settings), then it will return up to that many bundles. If you set the limit to 1 then it will return only 1 bundle.
Alternatively, if you put an aggregator after Airtable, you can aggregate the bundle into 1 before going on to the next module.
Without much detail about what you’re trying to achieve, I hope this bit helps you out.
Thanks Donald. To explain a bit more, this is an existing scenario whereas the data store element is the only new part that I’m adding.
My intention is to keep all relevant bundles from Airtable, but to only load the data store content once (instead of for each bundle) and thereafter go back to process all Airtable bundles.
The data store content changes only once a day and is so to say static, whereas the Airtable data is dynamics.
The obvious way would be to swap the position of the Airtable trigger and data store, but as I cannot just move but have to change/delete the trigger module, I would need to set up the following 70 modules from scratch, which is what I’m trying to avoid. I hope this makes sense.
