Skip to main content
Open

Attribute Accumulation - List only

Related products:Transformers
  • February 28, 2020
  • 5 replies
  • 44 views

michaelpascoe

Hello all,

I regularly perform a merge (eg. FeatureMerger) where I am only interested in generating a list on the requestor from the supplier and don't want any attributes merged other than the list.

In this case I usually set the Accumulation Mode to "Prefix Supplier" with a prefix of something like "_ignore_me" and then optionally use a BulkAttributeRemover to remove these merged attributes.

It would be nice to have an Accumulation Mode option like "Do not Merge" or "Only use List" such that only the list defined under "Generate List" is added the requestor and no other attributes are merged

This would also be useful in the other transformers that merge/accumulate attributes.

5 replies

ebygomm
Influencer
Forum|alt.badge.img+46
  • Influencer
  • February 28, 2020

I'd expand this to include cases like the neighbourfinder. It's already possible with this to untick merge attributes and tick generate list, but a number of attributes like _angle, _candidate_angle are still added to the feature. If I'm building a list and not merging attributes, I don't want to add any attributes to the feature outside of the list.


Forum|alt.badge.img+2
  • February 28, 2020

one possible option would be to add a field under merge attributes to select what attributes you want to merge. Similar to the Add to List: Selected Attributes | All. Would that work?


michaelpascoe

Yep, that would be perfect.


revesz
Contributor
Forum|alt.badge.img+21
  • Contributor
  • September 22, 2022

It would solve my problem as well

I have duplicate Suppliers, the Suppliers may have missing attribute.

When I run through the transformer and ListExplode the Supplier list on the Merged port, the missing attribute 'inherits' an existing value if first Supplier on the same key has that attribute. This is because exploding the list, the missing attribute value won't clear the attribute, which is already there from the first merged Supplier.

The 'untick merge attributes' would save me the mitigation workarounds.


s.jager
Influencer
Forum|alt.badge.img+23
  • Influencer
  • January 16, 2026

It’s an old Idea, but I just ran into the fact that attributes were added while I only wanted a list. An AttributeRemover solved my problem, but having the option of only adding a list would save an extra transformer. So bumping this up...