+5Hi,
I would like to use a simple function in the SchemaMapper for Attribute value for a new attribute. In an AttributeCreator I would use @Value(Lat)#@Value(Lng). This concatenates two values seperated by a #. I can't get it to work in a SchemaMapper. I tried @EvaluateExpression(@Value(Lat)#@Value(Lng)), but the SchemaMapper interprets this as a string and not a function. How can I make this work?
Btw, I use FME 2023.2.5.
Thank you, Arno
Best answer by debbiatsafe
Hello
Have you specified fmeexpression= in front of the expression concatenating the two values? For example, the CSV for the SchemaMapper should look like this:
TargetAttribute|TargetValue
latlong|fmeexpression=@Value(lat)#@Value(long)This should create a new attribute named latlong which concatenates the value of lat and long separated with #. You may need to expose the new attribute with an AttributeExposer or AttributeManager.
Please note that there is a bug (FMEENGINE-82741) where using fmeexpression= in the SchemaMapper will cause a space to be inserted at the start of target attribute value. This has been fixed in FME 2025.0 betas.
As you are using 2023.2, please use an AttributeTrimmer after the SchemaMapper to remove the space.
+21Hello
Have you specified fmeexpression= in front of the expression concatenating the two values? For example, the CSV for the SchemaMapper should look like this:
TargetAttribute|TargetValue
latlong|fmeexpression=@Value(lat)#@Value(long)This should create a new attribute named latlong which concatenates the value of lat and long separated with #. You may need to expose the new attribute with an AttributeExposer or AttributeManager.
Please note that there is a bug (FMEENGINE-82741) where using fmeexpression= in the SchemaMapper will cause a space to be inserted at the start of target attribute value. This has been fixed in FME 2025.0 betas.
As you are using 2023.2, please use an AttributeTrimmer after the SchemaMapper to remove the space.
+5
Thank you very much Debi, I did not know about the fmeexpression=, but it works great. I indeed get an extra space in front of the at the start of the target attribute value. I can fix that later in my workspace.