Skip to main content
Solved

CoordinateSystemSetter get error when use Conditional Value option?

  • July 20, 2026
  • 6 replies
  • 149 views

davidlee
Supporter
Forum|alt.badge.img+8

I'm constantly getting an error in FME 2026.2 whenever I use the 'Conditional Value' option in CoordinateSystemSetter transformer, regardless of the input values. Could this be a bug?

Best answer by daveatsafe

This problem seems to have been introduced by an update to the CoordinateSystemSetter for FME 2026.2. We are working on fixing it, but in the meantime, CoordinateSystemSetters placed in FME 2026.1 or earlier continue to work correctly in FME 2026.2.

I am attaching a small workspace containing aΒ CoordinateSystemSetter placed in FME 2026.1. You can cut and paste from this workspace in FME 2026.2 to avoid placing an updated transformer.

6 replies

redgeographics
VIP
Forum|alt.badge.img+63

It’s working for me.Β 

Can you share what the error is that you’re getting and how you have set up the conditional value?


davidlee
Supporter
Forum|alt.badge.img+8
  • Author
  • Supporter
  • July 21, 2026

It’s working for me.Β 

Can you share what the error is that you’re getting and how you have set up the conditional value?

I just have a simple test as follows:


Β 

And I have tried some conditional value at test statement but always get error:

β€œCoordinateSystemSetter (CoordinateSystemFactory): CoordinateSystemSetter: Invalid Test Expression: TEST@Value(_creation_instance)=1”

β€œCoordinateSystemSetter (CoordinateSystemFactory): CoordinateSystemSetter: Failed to evaluate input expression: FME_CONDITIONAL:DEFAULT_VALUE''BOOL_OP;OR;COMPOSITE_TEST;1;TEST@Value(_creation_instance)=1'LL-WGS84'FME_NUM_CONDITIONS2___”

β€œError running translation: CoordinateSystemSetter: Invalid Test Expression: TEST@Value(_creation_instance)=1. CoordinateSystemSetter: Failed to evaluate input expression: FME_CONDITIONAL:DEFAULT_VALUE''BOOL_OP;OR;COMPOSITE_TEST;1;TEST@Value(_creation_instance)=1'LL-WGS84'FME_NUM_CONDITIONS2___”

It only works with fixed-value coordinate systems:
Β 

Β 


redgeographics
VIP
Forum|alt.badge.img+63

That’s really strange. So yesterday when I said I tried it, I had used a User Paramter rather than an attribute value. Trying to recreate what you have and I’m getting the same errors.

Some things to look out for:

  • If you let the Creator create just one feature, it’s _creation_instance will be 0. I changed that in the conditional value, no change.
  • You’re currently creating a null geometry, I thought that that might throw the CoordinateSystemSetter off, but adding geometry doesn’tΒ make a difference.
  • You’re not adding a coordinate system to the Else part, I also tried that and no difference.

I also tried your setup but with a user parameter and that doesn’t work either all of a sudden...

I think you’re right and this may be a bug. Your best course of action is to submit this as a support ticket with either your local partner or Safe directly and refer them to this discussion.


max_h
Enthusiast
Forum|alt.badge.img+31
  • Enthusiast
  • July 21, 2026

I just tested it in 2026.1 and 2026.2:

in 2026.1 it worked fine
In 2026.2 I am getting the same errors, also in CoordinateExtractor
Β 

CoordinateExtractor_SPECIFIC_Z_ROUTER (TestFactory): CoordinateExtractor: Invalid Test Expression: TEST@Value(Test)=5


Conditional values in other transformers (e.g. localCoordinateSystemSetter, Bufferer, CoordinateRounder,AttributeManager) work fine

So it indeed looks like a bug to me

Β 

Β 

edit: ​@redgeographicsΒ  this time you beat me by a minute
Easiest workaround would be a TestFilter and then multiple CoordinateSystemSetter with fixed values for now.


davidlee
Supporter
Forum|alt.badge.img+8
  • Author
  • Supporter
  • July 22, 2026

I have submitted this to Safe as a support ticket! Β Hopefully it will be fix in the next version.Β πŸ˜€


daveatsafe
Safer
Forum|alt.badge.img+23
  • Safer
  • Best Answer
  • July 22, 2026

This problem seems to have been introduced by an update to the CoordinateSystemSetter for FME 2026.2. We are working on fixing it, but in the meantime, CoordinateSystemSetters placed in FME 2026.1 or earlier continue to work correctly in FME 2026.2.

I am attaching a small workspace containing aΒ CoordinateSystemSetter placed in FME 2026.1. You can cut and paste from this workspace in FME 2026.2 to avoid placing an updated transformer.