Skip to main content

We just updated to 2022.1 and now I'm getting an error when using the Tester.

That's what I did:

I  used a Creator and created an attribute "attr1" with the value 5 in an AttributeManager.

Now I add a Tester with "attr1 = 5" then I get this error:

 

Tester (TestFactory): The clause 'TEST { @EvaluateExpression(FDIV,STRING_ENCODED,<at>Value<openparen>attr1<closeparen>,Tester) = 5 ENCODED }' within 'FACTORY_DEF * TestFactory FACTORY_NAME Tester INPUT FEATURE_TYPE AttributeManager_OUTPUT TEST { @EvaluateExpression(FDIV,STRING_ENCODED,<at>Value<openparen>attr1<closeparen>,Tester) = 5 ENCODED } BOOLEAN_OPERATOR OR COMPOSITE_TEST_EXPR <Unused> FEATURE_TABLE_SHIM_SUPPORT Yes PRESERVE_FEATURE_ORDER PER_OUTPUT_PORT OUTPUT PASSED FEATURE_TYPE Tester_PASSED OUTPUT FAILED FEATURE_TYPE Tester_FAILED' is incorrect.  TEST must look like: TEST <value> <operator> <value> DENCODED]
The clause 'TEST { @EvaluateExpression(FDIV,STRING_ENCODED,<at>Value<openparen>attr1<closeparen>,Tester) = 5 ENCODED }' within 'FACTORY_DEF * TestFactory FACTORY_NAME Tester INPUT FEATURE_TYPE AttributeManager_OUTPUT TEST { @EvaluateExpression(FDIV,STRING_ENCODED,<at>Value<openparen>attr1<closeparen>,Tester) = 5 ENCODED } BOOLEAN_OPERATOR OR COMPOSITE_TEST_EXPR <Unused> FEATURE_TABLE_SHIM_SUPPORT Yes PRESERVE_FEATURE_ORDER PER_OUTPUT_PORT OUTPUT PASSED FEATURE_TYPE Tester_PASSED OUTPUT FAILED FEATURE_TYPE Tester_FAILED' is incorrect.  TEST must look like: TEST <value> <operator> <value> rENCODED]

I know that there have been some changes with the encoding in FME and that there are some limitations regarding the operating system. 

So we're running FME on a Windows Server 2016 (no service pack)

 

Do I have to apply some settings or what could be the reason for this error?

 

Thanks

Vera

image


So how did you set up your Tester? Like this? This should work.

Tester_Parameters


imageIt's not working...

 


So can you share the contents of your Tester?


image


Hmmm, looks exactly the same to me. Sorry, wanted to be sure about that.

I fear I can't help you here, hopefully somebody else can shed some light.


2022_1Seem to work for me as well. Only different would be Window Server environment?


image

Maybe you can upgrade the tester​, or configure a new one?


We will update the Server to WindowsServer 2022 and try again then. Thanks.


Reply