One possible way below. Because of the way the attributes are renamed, they need to be exposed later.
It works great! I don't understand why the Aggregator stores attributes in the background and lists are not generated.
I still have a lot to learn before I get such a great background knowledge! Thank you very much!
In this case the Aggregator does not create a list, because I did not set that option. The attributes are renamed before they enter the Aggregator, so they will all have unique names across all features. As the Aggregator is set to Merge Incoming Attributes, all attributes will be added to the aggregated feature.
And the attributes are not exposed because of the way they are renamed, so they need to be exposed later.
Thanks for that. The aggregator only creates a row. But I have over 300 rows. With the list function I dit not get useful results. What to do to get multiple rows?
In the Aggregator use Group By on the attribute(s) that determines which features belong to the same row.
The picture shows a similar initial table.
The picture shows a similar initial situation (initial table).
Thank you for the new example data set.
I have marked the changes from the previous workspace:
I found the solution: In BulkAttributeRenamer keep modus origin attributes and remove Attrbute Exposer and Attribute Remover.