Skip to main content
  • EN

Folks,

This is part observation and part confirmation of the general functionality of Transformers.

I have an AttributeManager. Amongst it's operations there is a conditional evaluation of a value.

If owner = XCOM then id = 0. This modified the id value. This was working. Then "all of a sudden" it stopped working.

During my manipulations I applied another modification to the owner field in the same AttributeManager.

If owner = XCOM then owner = Xcom. This modified the owner field. A case modification for the purposes of output.

What I didn't anticipate was that my earlier condition would stop working because the case of the owner had changed based on another condition.

I presumed that all operations in an AttributeManager operated on the original input file values.

Is this expected functionality?

Expected functionality

There is the option to define order

Hi @andyew,

The order of the operations is important in the AttributeManager so if your second operation comes before the first one ( what doesnt make sense I realized while typing...) then the behavior is to be expected.

Expected functionality

There is the option to define order

tricky to get head around when first arrived :)

 

 

the order in a attribute creator is important in 2015, 2016 as well. When you are using attributes manipulated in a prior rule it will effect subsequent use in same attribute creator. Like chaining them.

Reply


Community Stats

30,133
Posts
114,389
Replies
37,772
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.