Expected behaviour or a bug (or user error?)
Expected behaviour or a bug (or user error?)
you didn't specify which version of FME, but it seems to work fine with FME2013 SP2.
If you use an older version, I suggest you use an AttributeRenamer first to retrieve the value into an ordinary non-list attribute.
David
If you simply rename the attribute and use that as the Requestor Join Attribute this doesn't appear to work either. Using exactly the same data and using a listexploder results in features passing out the complete port...
Could you perhaps post a screenshot of your merger settings along with a couple of sample features?
David
I tested the ListIndexcer, AttributeCreator, AttributeRenamer, exposing directly to change the first element of a list to a non-list attribute, and all worked successfully in the FeatureMerger (FME 2013 SP1). Actually, where the list came from? I have seen a case lacking the first element when a list contains flattened XML element values from the XML reader or the XMLFlattener.
Takashi
Adding an attributetrimmer (not specifying any trim characters) after the attributerenamer in the first workbench also results in features being successfully merged, although the stringlength remains unchanged for every feature after trimming??