I'm trying to use the AttributeManager to rename an attribute and at the same time set a value using a conditional formula. Should this be possible?
Question
AttributeManager - expected behaviour?
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.
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.
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.
+46- Influencer
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 managed it in a similar way by setting the value of the original attribute first and then renaming it in a later step.
+3Hi @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.