+4Hello, I want to replace the list of attributes of the ChangeDetector with a user parameter. The attributes of the original and revised features are not exposed. The user parameter is in Python: it's a string derived from another parameter (example: 'field1 field2 field3'). I don't get any error but I guess values are not considered.
I have the same problem with other transformers based on the same attribute list type (AttributeExposer).
It is an issue or a problem with the string? Thank you
Best answer by markatsafe
@dhaulagiri ChangeDetector does accept a parameter:
Try creating the parameter in the ChangeDetector and then link that to your python parameter.
AttributeExposer will not accept a dynamic list of attributes because it's an 'authoring' tool and adds attributes to the workbench schema. Adding attributes in AttributeExposer will add attributes down stream, like AttributeManager, which can't be done dynamically. In most cases, just because attributes are not exposed in the workbench schema, they are still on the features and will be written out.
@dhaulagiri ChangeDetector does accept a parameter:
Try creating the parameter in the ChangeDetector and then link that to your python parameter.
AttributeExposer will not accept a dynamic list of attributes because it's an 'authoring' tool and adds attributes to the workbench schema. Adding attributes in AttributeExposer will add attributes down stream, like AttributeManager, which can't be done dynamically. In most cases, just because attributes are not exposed in the workbench schema, they are still on the features and will be written out.
+4@Mark Stoakes , you have unlocked the situation, thank you! This solution works perfectly. I was candid in thinking that it was enough for the parameter to simply return a string formatted like what you see when you just select attributes. It's apparently a bit more than that!
For AttributeExposer, I wrote too quickly: it is correct that it is different. Actually, I meant CRCCalculator, which is also right next to it in my workbench. Whoops.
I retain that it is preferable to create the user parameter directly in the transformer which uses it.
+4Hello,
For 2 years, the solution proposed in this post worked perfectly. But I recently noticed that the ChangeDetector was no longer doing its job and was no longer detecting the parameter correctly. The script has not been modified. Only a version upgrade was performed: 2022 to 2024. It hasn't been done recently. So I don't understand why this problem is happening now. Do you have any idea?
I can also use this problem to say how disappointed I am that I can no longer benefit from a free FME home license. Before, I could learn and work on this kind of very specific problem at home, quietly (and with pleasure!). Now I can't. I have to do it at work, and I don't have the time. So I'm doing less training and using FME less. It's a real shame...
+14Hello,
For 2 years, the solution proposed in this post worked perfectly. But I recently noticed that the ChangeDetector was no longer doing its job and was no longer detecting the parameter correctly. The script has not been modified. Only a version upgrade was performed: 2022 to 2024. It hasn't been done recently. So I don't understand why this problem is happening now. Do you have any idea?
I can also use this problem to say how disappointed I am that I can no longer benefit from a free FME home license. Before, I could learn and work on this kind of very specific problem at home, quietly (and with pleasure!). Now I can't. I have to do it at work, and I don't have the time. So I'm doing less training and using FME less. It's a real shame...
Rather than depending on free home license for FME, you should look at using the license of your employer or asking your employer to make arrangements for access to FME license remotely, since with FME Form, fixed and floating licenses are priced the same.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
