Skip to main content
  • EN

Hi list.

I was under the impression, that every single transformer in a workspace had its own set of parameters.

However, I now have a custom transformer in my workspace, which contains two FeatureReaders, both targeting WFS. They seems to have a shared parameter set.

Whenever I change the parameters in one of the FeatureReaders, the parameters in the other FeatureReader mirrors those parameters exactly.

This works both way, whenever I change one, the other changes too, which makes me suspect a shared parameter set.

What gives ?

Is this because they are embedded within a custom transformer ?

Please advise.

Cheers.

Using 2020.2

Whats likely happened is that both transformers are using the same parameters (which is a totally valid workflow) So when you change the parameter value, both transformers use that same value. In one of the transformers you need to Create (a new) User Parameter

 

Screenshot 2021-05-20 083643

Whats likely happened is that both transformers are using the same parameters (which is a totally valid workflow) So when you change the parameter value, both transformers use that same value. In one of the transformers you need to Create (a new) User Parameter

 

Screenshot 2021-05-20 083643

No, it concerns the "Parameters" button on the left (with a red exclamation point), not user parameters.

No, it concerns the "Parameters" button on the left (with a red exclamation point), not user parameters.

Right, I follow. I gave it a go and can't seem to replicate your issue. Might be worth touching base with Safe Support and seeing its a bug

No, it concerns the "Parameters" button on the left (with a red exclamation point), not user parameters.

No worries. I most likely was too wrapped up with the problem, failing to properly describe the problem adequately. Kinda "I know what parameters we're talking about, so does everyone else" 🙂 Happens often for me when I'm dug deep into a problem.

I was giving the community a shot before escalating it to support. But I do see it as a potential bug, but haven't tested it with 2021 yet, as it eventually needs to go onto a FME Server, which still runs 2020.2.

Funny enough, I back-ported my workspace to 2018.1, and here it works as expected. I always keep the old desktop versions hanging on for just such an occasion.

Cheers.

Reply


Community Stats

30,159
Posts
114,479
Replies
37,802
Members
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.