Skip to main content
Question

Shared FME folders regarding custom transformer

  • June 11, 2019
  • 3 replies
  • 36 views
K
Forum|alt.badge.img

Good day,

 

I created a custom transformer (*.fmx file) that is used across different workbenches and users.

 

To use the custom transformer I specify the location on FME Options - Default Paths - Shared FME folders.

 

This custom transformer is saved in two different locations with teh same name depending on what database and some other variables we are using.

 

Where can I specify the one I want to use in a script?

 

Is there any parameter in a workbench I can set to point to the correct shared fme folder for this specific workbench?

 

The shared fme folder I want to use is depending on the script I am running.

 

Thank you.
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.

3 replies

jdh
Contributor
Forum|alt.badge.img+40
  • jdhContributor
  • Contributor
  • June 11, 2019

Having multiple custom transformers with the same name is generally a recipe for conflicts. Could you add a prefix or suffix to the transformer name?

K
Forum|alt.badge.img
  • kat
  • Author
  • June 11, 2019

We have an automated deployment process in place that we only need to do the changes in one custom transformer and the change will be deployed to the customers transformers importing to dif dbs.

mark2atsafe
Safer
Forum|alt.badge.img+59

I think the usual technique is to have one transformer with published parameters. Then the user picks the database, etc to use when they put the transformer in the workspace, using those parameters.

The only other way I see is to have two versions of the transformer (by which I mean set up versioning of the transformer when you edit it). Then you *might* be able to keep version 1 for db1 and version 2 for db2 - but I'm not sure how feasible it is switching versions in a workspace. I don't really think versioning is meant for that scenario. Published parameters would be much better.

FME Evangelist to the Rich and Famous!!

Community Stats

32,181
Posts
122,172
Replies
39,855
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.