+14Hi,
when I replace the hardcoded string to a dataset with a parameter (in my case my $(FME_SHAREDSOURCE_DATA) Resources), the FeatureReader destroys all my 'one per feature type' or 'specified' Output Ports. Even if I add 'FeatureTypes to Read' as a Fixed List parameter.
So how can I make the Output Ports persistent to prepare my workspace for FME Server?
(FME 2017.1.1.0 build 17650)
Best answer by david_r
The easiest, in my opinion, is to use the Single Output Port option followed by a TestFilter on fme_feature_type or fme_dataset.
You can, however, accomplish what you want by linking the transformer dataset property to the FME_SHAREDRESOURCE_DATA parameter from the Navigator / Transformers list, rather than from the transformer properties:
This should enable you to set a different dataset while preserving your existing output ports.
The easiest, in my opinion, is to use the Single Output Port option followed by a TestFilter on fme_feature_type or fme_dataset.
You can, however, accomplish what you want by linking the transformer dataset property to the FME_SHAREDRESOURCE_DATA parameter from the Navigator / Transformers list, rather than from the transformer properties:
This should enable you to set a different dataset while preserving your existing output ports.
+14The easiest, in my opinion, is to use the Single Output Port option followed by a TestFilter on fme_feature_type or fme_dataset.
You can, however, accomplish what you want by linking the transformer dataset property to the FME_SHAREDRESOURCE_DATA parameter from the Navigator / Transformers list, rather than from the transformer properties:
This should enable you to set a different dataset while preserving your existing output ports.
+14@david_r
Your suggestion works pretty good (applying the parameter from the Navigator instead of the transformer properties). Thanks a lot.
