When I enter $(user_parameter) as user attribute name, it will be replaced to $_user_parameter_
Hi @nlaszlo1976, where are you setting this attribute up? On the Feature Type or earlier in the workspace with an AttributeManager?
Hi @nlaszlo1976, I guess you have entered it to the 'Name' column in the User Attributes tab in the Oracle writer feature type.
In the User Attributes tab in a writer feature type, you will have to define an attribute name with a literal string, cannot set it referring either a user parameter value or a feature attribute value.
FME Workbench considers the string you have entered as a field name literally. However, in the Oracle naming conventions, since brackets aren't allowed to be contained in a field name, FME Workbench has replaced them with underscores automatically.
Hi @nlaszlo1976, I guess you have entered it to the 'Name' column in the User Attributes tab in the Oracle writer feature type.
In the User Attributes tab in a writer feature type, you will have to define an attribute name with a literal string, cannot set it referring either a user parameter value or a feature attribute value.
FME Workbench considers the string you have entered as a field name literally. However, in the Oracle naming conventions, since brackets aren't allowed to be contained in a field name, FME Workbench has replaced them with underscores automatically.
calc-totalroadlength-dialog.fmw
calc-totalroadlength-dialog.fmw
Hi @nlaszlo1976, I guess you have entered it to the 'Name' column in the User Attributes tab in the Oracle writer feature type.
In the User Attributes tab in a writer feature type, you will have to define an attribute name with a literal string, cannot set it referring either a user parameter value or a feature attribute value.
FME Workbench considers the string you have entered as a field name literally. However, in the Oracle naming conventions, since brackets aren't allowed to be contained in a field name, FME Workbench has replaced them with underscores automatically.
Alternatively, the SQLExecutor could also be used to execute an SQL (UPDATE) statement. I think you can construct an appropriate SQL statement using the values of the feature attributes and user parameters.