Skip to main content
  • EN

Hello All,

I’m having an issue where SchemaMapper prefix whitespace (space) when using fmeexpression=.

I attached a sample workspace and would appreciate if anyone could test before submitting ticket.

 

This issue came apparent after upgrading to FME 2023. for example: col0=’2’, col1=’3’-->using “fmeexpression=@Evaluate(@Value(col0)+@Value(col1))” returns value “ 5” or “fmeexpression=@Evaluate(@Value(col0)@Value(col1))” returns value “ 23”

Previously, using “@Evaluate(rreturn “@Value(col0)@Value(col1)])” returns value “23”. 

I know 2023 introduced new functionality to SchemaMapper, per transformer help doc and https://support.safe.com/hc/en-us/articles/25407523665165-SchemaMapper-Advanced-Schema-Mapping. 

 

Would appreciated if someone could test before submitting ticket.
 

Output


 

SchemaMapperDoc

 

Hello @alexlynch3450 

I’m sorry you have encountered this issue. This behaviour has already been reported and is tracked as FMEENGINE-82741. I will update this thread once this has been resolved.

The workaround is to use an AttributeTrimmer after the SchemaMapper to remove the leading whitespace. I hope this information helps!

dang, that’s counterproductive. I’d have to add both attributeExposer and AttributeTrimmer to every attribute occurrence. Quite literally defeats dynamic writing. please please please update this. 

Reply


Community Stats

30,356
Posts
115,368
Replies
38,093
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.