+54I probably found a discrepancy in the StringReplacer but would like to check.
In the Attributes field not only Attributes but also User Parameters are selectable. Nothing seems to happen, and I think this is correct behaviour, or am I missing something?
Checked in Workbench 2018.1.1.0
Best answer by redgeographics
FME expects that parameter to be one or more attribute names that are to be processed by the StringReplacer. If you add a source dataset and use that parameter to pick an attribute from it, it works as intended.
So FME doesn't change the value of the user parameter and the way I see it, that's expected behaviour.
+50FME expects that parameter to be one or more attribute names that are to be processed by the StringReplacer. If you add a source dataset and use that parameter to pick an attribute from it, it works as intended.
So FME doesn't change the value of the user parameter and the way I see it, that's expected behaviour.
+54FME expects that parameter to be one or more attribute names that are to be processed by the StringReplacer. If you add a source dataset and use that parameter to pick an attribute from it, it works as intended.
So FME doesn't change the value of the user parameter and the way I see it, that's expected behaviour.
I understand and agree. But if you can not change the Parameters, you should not be able to be select them?
+50I understand and agree. But if you can not change the Parameters, you should not be able to be select them?
You use the parameter if you want to let the user select an attribute for the StringReplacer at runtime.
+54You use the parameter if you want to let the user select an attribute for the StringReplacer at runtime.
Ah, thanks Hans! I'm slow.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
