Skip to main content
Solved

AttributeManager somewhat unexpected functionality

  • May 18, 2017
  • 4 replies
  • 26 views

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?

Best answer by mark_f

Expected functionality

There is the option to define order

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.

4 replies

Forum|alt.badge.img+2
  • Best Answer
  • May 18, 2017

Expected functionality

There is the option to define order


itay
Supporter
Forum|alt.badge.img+18
  • Supporter
  • May 18, 2017

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.


Forum|alt.badge.img+2
  • May 18, 2017

Expected functionality

There is the option to define order

tricky to get head around when first arrived :)

 

 


gio
Contributor
Forum|alt.badge.img+15
  • Contributor
  • May 18, 2017

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.