AttributeManager - expected behaviour?

Do you mean like this?attributemanager.fmw

Hi @egomm

it looks like AttributeManager deals with renaming first and by the time it needs to evaluate @Value(_creation_instance) = 0 there is no _creation_instance attribute. I have filed a PR asking to investigate if AttributeManager behaviour can be improved. For now, I would like to suggest

• calculating the value and assigning it to the new attribute first and then
• removing the old attribute,

i.e. two steps/lines in AttributeManager.

Hi @egomm

it looks like AttributeManager deals with renaming first and by the time it needs to evaluate @Value(_creation_instance) = 0 there is no _creation_instance attribute. I have filed a PR asking to investigate if AttributeManager behaviour can be improved. For now, I would like to suggest

• calculating the value and assigning it to the new attribute first and then
• removing the old attribute,

i.e. two steps/lines in AttributeManager.

I figured this was the reason. But if I try to use the new name for the attribute (e. g. "Order" instead of "_creation_instance") when setting up the conditional values, I cannot get an attribute with the new name ("Order"), only an attribute with the old name ("_creation_instance"). (I use FME 2016.1 build 16609, by the way).