Array Aggregator Selection Issues When Dealing With Different Variables Spanning Multiple Operations

Hey Guys,

I’m running into an issue when constructing a particular kind of scenario. In short, I have a ‘Set Multiple Variables’ module that is set to output slightly differently named variables per operation. However, when I go to select those variables to be output by the Array Aggregator, only the variables that are output in operation 1 appear in the list, rather than listing all the variables from all of the operations.

To provide some more context: I’m trying to do a sort of complex transposing of data from a CSV into a Baserow database. The source data comes from a CSV generated by Bearable, a symptom/health tracking app. The symptom ratings are lumped into 4 different time slots in a day: pre, am, mid, pm. I’m trying to take these variables, which are tracked as separate rows in the original csv data, and lump them all into one row in my database. In order to achieve this, I need to create 4 categories for each symptom that associate with a column in my database (e.g. Arm Numbness (pre), Arm Numbness (am), Arm Numbness (mid), Arm Numbness (pm)).

I need to be able to aggregate all instances of these variables, not just the ‘pre’ instances.

Anyone have any ideas?

Thanks for reading!

Hey there,

so you have a CSV that you are filtering and aggregating the remaining items, then creating some variables and you want to add them to the same array? If this is the case, then move the Tools module after the filter before the first aggregator.

So that first array aggregator was there to group the csv data by date and time slot, in an attempt to transpose the data. Every which way I configured the array aggregators and iterators, I could not easily figure out how to reformat the data so that I’d have all possible variables in one array, along with the correct amount of operations when inputting into my baserow.

After a bunch of messing around, I ended up just having to build the scenario a completely different way. I actually did put the ‘set variable’ module right after the router, and instead built out a JSON string in the exact structure I wanted, followed by a parse JSON module. While this uses much more operations, it does the job.

I’ll leave this open a little longer if anyone has a definitive answer to my original question about how the array aggregator works, and if there’s some way it can recognize objects from different operations.