Skip to main content
  • EN

FME 2025.0.2.0

I’ve built an embedded custom transformer which uses a web connection as a parameter.

When I initially use the custom transformer in my workspace I’m able to specify a deployment parameter for the value of the web connection.

e.g. 

 

However, as soon as I close and re-open the transformer properties the connection becomes invalid and the OK button is disabled:

 

It’s not possible to re-assign the deployment parameter as the connection value unless I first clear it, then re-add it.

I’ve tried various workarounds (e.g. creating a standard published parameter to hold the deployment parameter value) but I can’t get this to behave like I think it should.

Has anyone been able to successfully use deployment parameters for web connection values in a custom transformer?

Also, not sure if it makes a difference but I’m using a custom web service for my web connection.

 

I can only think of a workaround where you place ParameterFetcher prior to the custom transformer, writing the value to an attribute that you specify in the Custom Trans - published parameter.

You may wish to raise this to Safe support https://support.safe.com/hc/en-us/p/Support referencing this URL post.

I can only think of a workaround where you place ParameterFetcher prior to the custom transformer, writing the value to an attribute that you specify in the Custom Trans - published parameter.

You may wish to raise this to Safe support https://support.safe.com/hc/en-us/p/Support referencing this URL post.

 

Thanks for the suggestion. Unfortunately using the ParameterFetcher exhibits the same behaviour.

I’ll submit a support ticket to Safe.

Community Stats

31,852
Posts
120,987
Replies
39,485
Members

Latest FME

Terms & ConditionsCookie settings
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.