Issue with SchemaScanner Misinterpreting ID Field Data Type

I think adding a space to OBJ_ID as a suffix using an AttributeCreator before the SchemaScanner and remove this space afte the SchemaScanner using an AttributeTrimmer should work. It is hacky and a workaround, but I think it does what you need.

A space did not work but adding # worked however fme_varchar(23) of course instead fme_varchar(22). Do you know why SchemaScanner messes up  like this? 

It tries to interpret the data type, but why this results in a scientific notation, I do not know. What data format are you writing to?

As to the char 22 vs char 23, you probably can solve this by inserting a dummy feature with a dummy 22 character string as id in the stream before the SchemaScanner and remove this feature after the SchemaScanner. This is probably more performance efficient as well.

Can you not set the type explicitly in an AttributeManager prior to the schemascanner?

​@ebygomm What do you mean explicitly? When I add AttributeManager, it immediately recognizes varchar(22) and SchemaScanner still think it is fme_real64 although I added AttribiteManager