Skip to main content
  • EN

A parameter is like an argument that is static. A variable, however, represents a state and can be dynamically created and assigned in a workspace. I wish FME workspace UI exposes variables the same way it exposes parameters or attributes. Converting variables to attributes via VariableRetriever does not help, as attributes are about content while variables are about states and flow control.

I am in agreement with @bambography in his or her post.

https://knowledge.safe.com/questions/34563/can-global-variables-be-accessed-as-values-in-tran.html

I agree, there needs to be better support for using variables without using dedicated transformers (VariableSetter / VariableRetriever). My preference would be to add the following:

Function call, e.g.

@Variable(_my_variable)

Python API, e.g.

value = fmeobjects.FMESession().getVariable('_my_variable') fmeobjects.FMESession().setVariable('_my_variable', 'My Value')

 

 

At the very least the VariableRetriever should be a dropdown list of all the variable names used in a variableSetter.

Oh yes this would make things a lot easier. I would love to use a tester based on the value of a variable in the same way. Having to retrieve the variable as an attribute and then test is a real pain.

 

Also not being able to retrieve multiple variables with one VariableRetriever is another pet peeve (https://community.safe.com/s/idea/0874Q000000TlDuQAK/detail) also https://community.safe.com/s/idea/0874Q000000TkzIQAS/detail

 

Also what David said!

The following idea has been merged into this idea:

All the votes have been transferred into this idea.
The following idea has been merged into this idea:

All the votes have been transferred into this idea.

Community Stats

31,841
Posts
120,927
Replies
39,472
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.