One possible way using an attribute exploder
Find_max_across_attributes.fmwt
You could do it with a conditional in an AttributeCreator/Manager.
This does evaluate the max twice, alternative you could create a temp attribute storing the max, and have the conditional check if A = maxVal etc.
This workflow could also be possible. The ListElementFilter is a custom transformer from the FME Hub.
This workflow could also be possible. The ListElementFilter is a custom transformer from the FME Hub.
Interesting use of the AttributeExploder. It would be nice if there was a parameter to exclude hidden fme/reader attributes
This workflow could also be possible. The ListElementFilter is a custom transformer from the FME Hub.
I hope "Selected Attributes" parameter will be added to the AttributeExploder, so that the user can select attributes to be exploded or NOT to be exploded optionally.
See also this Idea.
Option to Select Attributes that should not be Exploded in AttributeExploder