Skip to main content
Question

Change connection file in mid transformation

  • April 25, 2018
  • 2 replies
  • 15 views

Forum|alt.badge.img

Help. I'm trying to write several tables (ESRI geodatabase, not file geodatabase), based on a csv on input tables to the identical schema on the output (ie SCHEMA1.TABLE1 -> SCHEMA1.TABLE, SCHEMA2.TABLE1 -> SCHEMA2.TABLE1). My latest attempt is to have connection files for each SCHEMA and generate an attribute with the path to the connection file, then in a featurewriter I set the connection file to be that attribute, but it's only using the first connection file path and ignoring others coming in. This process will expand to other tables in other schema's so I'm trying to make it as adaptable as possible.

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.

2 replies

david_r
Celebrity
  • April 25, 2018

I suspect it's not possible to change the connection file during translation.

You may want to use a child workspace with the connection file as a parameter. You can then invoke the child workspace using either the WorkspaceRunner or the FMEServerJobSubmitter.


erik_jan
Contributor
Forum|alt.badge.img+26
  • Contributor
  • April 25, 2018

Can you use multiple FeatureWriters (one per connection file) and the based on the attribute (AttributeFilter) pass the features to the right FeatureWriter?

It seems a bit more work, but could be easier to maintain.

Depends on the number of different connection files.