Please find attached the workflow diagrams and csv file used in FME.
Question
How to configure schema mapper which is dynamically fed by feature reader and use attribute mapping lookup table in the form of csv?
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+4- Contributor
- 23 replies
You can map attributes from an attribute mapping source using the 2016 FMEServerJobsubmitter to a generic data source. The values need to be saved as "@VAlue(attributeValue) and passed to a second workbench.
This woks in 2016, however there is a bug in the 2017 FMEServerJobSubmitter that is supposed to be fixed in 2018.
+9- Safer
- 284 replies
Hi @shashifile, thanks for your question!
In terms of the SchemaMapper working "dynamically", is the range of possible values of your input or output attributes known? If either one is, it might make sense to simply hand code conditional statements to account for each possibility. You might also want to explore the possibilities of a dynamic workflow.
Providing more information here or on your other related threads might help us narrow down a solution.
Hope this helps.
Nathan