Thank you.I've tried using the AttributeValidator,but that transformer throws an error when I'm using a attribute value as "upper limit value".If I manually set the limit,it works.This is the error-message:

Illegal operator `RANGE' supplied for test evaluation -- operator must be one of < > <= >= != = ==

I would go with the AttributeManager using conditional functionality.You don't want a "filter" transformer because you want to just test/set values,not filter the data.You really need a "mapper" transformer.The AttributeRangeMapper would probably work here,but in general we need to implement a mapper transformer that is similar to the conditional tools,but easier to find/understand.

嗨@torbjornd,if you are looking for a way to merge the limit values to the features from the SQLExecutor,the FeatureMerger might help you.You can set an identical constant (e.g.1) to the "Join One" parameter for both Requestor and Supplier,to merge Supplier's attributes to Requestors unconditionally.

i would go for a attributecreator ( manager in 2016 i believe).

Either use conditional creation (as stated by Rycharge) or use expression or regexp.to do that.

The TestFilter is using an If ..Elsif..Else construction.

So if the first test passes the other tests will not be executed.

If your feature fails all conditions only one output will be shown.

If you need all tests to be performed I would go with 5 Testers and connect the Passed port (Value > limit) to an AttributeCreator and route both streams to the next Tester.

This way all tests are performed and possibly 5 result attributes are created.

Attribute Manager conditional statements are good as well.Basically if you have a database that is centered around the use of drop down lists or there is a finite amount of acceptable values in a column then you can use if statements to check that all values are acceptable,if not then do nothing/change to null/flag it or set a default value for it.AttributeValidator is fantastic for checking exactly why a validation was failed,I believe the transformer creates a column _fme_validation_message.And it states why a record failed and exactly WHERE it failed,which is invaluable for troubleshooting validation problems.Hope this helps :)

嗨

Have you considered the AttributeValidator that was introduced in FME 2016?

David