Skip to main content
Solved

Does FME2026.x change the way decimal numbers are recognized?

  • July 27, 2026
  • 1 reply
  • 89 views

davidlee
Supporter
Forum|alt.badge.img+9

In FME 2026.x, the way Double data types are identified seems to have changed. Decimal numbers are only recognized as double when using a period ('.') as the separator, whereas a comma (',') is not. This is quite unusual, unlike previous versions which worked perfectly fine with commas.

I believe the identification method in previous versions was more efficient. For large workspaces, it could save us from using additional Transformers to convert commas to periods. Moreover, since input data formats in different regions still use commas as decimal separators, keeping the old identification logic would be much more flexible.
 

 

Best answer by desiree_at_safe

Hi ​@davidlee! Sorry to hear you've run into this! You're right, this is an unexpected change in behavior introduced in recent builds of FME.

I’ve raised an issue with our development team to get this resolved. In the meantime, as a temporary workaround, you can use a StringReplacer to swap commas (,) to periods (.) prior to your validation or data type checks (and convert them back before writing if your output requires commas).

[Internal Reference: FMEENGINE-99109]

I'll update this thread once a fix is available! 🙂

1 reply

desiree_at_safe
Safer
Forum|alt.badge.img+24

Hi ​@davidlee! Sorry to hear you've run into this! You're right, this is an unexpected change in behavior introduced in recent builds of FME.

I’ve raised an issue with our development team to get this resolved. In the meantime, as a temporary workaround, you can use a StringReplacer to swap commas (,) to periods (.) prior to your validation or data type checks (and convert them back before writing if your output requires commas).

[Internal Reference: FMEENGINE-99109]

I'll update this thread once a fix is available! 🙂