Sammeeey/arrayAggregatorNameBug

## arrayAggregatorNameBug
## What happens

I’m trying to aggregate multiple variables using an array aggregator.
More precisely I’m trying to aggregate names and GIDs of projects and tasks in Asana from the output of different modules in before the aggregator.

The issue:
I can pick the variables in the UI of the array aggregator and save it.
But when I open the array aggregator again, certain fields are always unselected.
”Coincidentally”🪄 the unselected fields are those which have the same `raw` name as other variables from the iterator before (Same thing happens when I choose “Select All” in the array aggregator).

## Workaround

A messy workaround would be:
Identify the duplicate variables (which can’t be saved and retained in the array aggregator):

1. in array aggregator select “select all” for the aggregated fields and click save
2. re-open array aggregator & identify variables which are unchecked in aggregated fields
3. create a “set multiple variables” module right in front of the array aggregator
4. create variables with new names for the unchecked variables in the array aggregator by mapping the output from the original module to the new variable name in “set multiple variables”
5. open array aggregator and select the new variables from “set multiple variables”

## What I expect

It should be possible to select variables from multiple different modules in an array aggregator (without the workaround) - even if they share the same raw name as variables in other modules.
Make should take care of re-assigning correct raw names to all the aggregated fields and should not simply unselect fields unexpectedly).

This is a bug report @Michaela & @vendy  - just like https://community.make.com/t/bug-in-array-aggregator-cant-access-collection-inside-array-from-ui/91781?u=samuelhartmann
This time I didn’t share it with the support, but [you can find an example scenario demonstating the bug here](https://eu2.make.com/1338821/scenarios/7636277/edit).
Could you please get the product dev team to fix this?!

P.S. Would also be a really helpful feature if one could assign new variables names to aggregated fields inside the array aggregator directly (regardless of the bug described above).
	## What happens

	I’m trying to aggregate multiple variables using an array aggregator.
	More precisely I’m trying to aggregate names and GIDs of projects and tasks in Asana from the output of different modules in before the aggregator.

	The issue:
	I can pick the variables in the UI of the array aggregator and save it.
	But when I open the array aggregator again, certain fields are always unselected.
	”Coincidentally”🪄 the unselected fields are those which have the same `raw` name as other variables from the iterator before (Same thing happens when I choose “Select All” in the array aggregator).

	## Workaround

	A messy workaround would be:
	Identify the duplicate variables (which can’t be saved and retained in the array aggregator):

	1. in array aggregator select “select all” for the aggregated fields and click save
	2. re-open array aggregator & identify variables which are unchecked in aggregated fields
	3. create a “set multiple variables” module right in front of the array aggregator
	4. create variables with new names for the unchecked variables in the array aggregator by mapping the output from the original module to the new variable name in “set multiple variables”
	5. open array aggregator and select the new variables from “set multiple variables”

	## What I expect

	It should be possible to select variables from multiple different modules in an array aggregator (without the workaround) - even if they share the same raw name as variables in other modules.
	Make should take care of re-assigning correct raw names to all the aggregated fields and should not simply unselect fields unexpectedly).

	This is a bug report @Michaela & @vendy - just like https://community.make.com/t/bug-in-array-aggregator-cant-access-collection-inside-array-from-ui/91781?u=samuelhartmann
	This time I didn’t share it with the support, but [you can find an example scenario demonstating the bug here](https://eu2.make.com/1338821/scenarios/7636277/edit).
	Could you please get the product dev team to fix this?!

	P.S. Would also be a really helpful feature if one could assign new variables names to aggregated fields inside the array aggregator directly (regardless of the bug described above).
No results found