Skip to main content
Solved

Changing Feature Reader source dataset but keeping existing feature types/output ports?

  • January 31, 2017
  • 2 replies
  • 88 views

chriswilson
Enthusiast
Forum|alt.badge.img+21

I am looking to adapt an existing workspace containing a feature reader that reads in an ESRI geodatabase with certain existing feature types to read and corresponding output ports for those feature types. The feature reader's source dataset path is set to a folder containing multiple geodatabases, with the particular geodatabase in that folder to be read being set dynamically depending on the fme_basename for another gdb that is read into the workspace beforehand. I'm looking to change the folder that the feature reader looks in, but keep the feature types to read and also the output ports the same - however when I try to do this and even if I specify the output ports the feature reader loses all output ports save for schema, generic and initiator. How do I avoid this?

Best answer by itay

by using the generic port, this will stay that way also if you change the input.

This has a downside and that is that you will need to expose any attributes use later in the translation.

Hope this helps.

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

itay
Supporter
Forum|alt.badge.img+18
  • Supporter
  • Best Answer
  • January 31, 2017

by using the generic port, this will stay that way also if you change the input.

This has a downside and that is that you will need to expose any attributes use later in the translation.

Hope this helps.


chriswilson
Enthusiast
Forum|alt.badge.img+21
  • Author
  • Enthusiast
  • January 31, 2017

by using the generic port, this will stay that way also if you change the input.

This has a downside and that is that you will need to expose any attributes use later in the translation.

Hope this helps.

Looks like a potentially helpful workaround so thanks for that, but it would be good if I could keep the specific and separate output ports.