Attribute management. Results of syncing attributes via the manager.

[Stefan Videnov]

Dear colleagues,

Based on @scottjm 's amazing presentation I tried to answer all my questions about how attribute messes are created, but there seems to be more. For example profiles seem to be more tricky. Additionally Associated attributes often get duplicated even when everything is reserved. I created another flowchart about syncing attributes via the manager, which should answer most of these questions.

I have two goals:
1. Bounce my flowchart with all of you about importing attributes and see if you can find something untrue or lacking in the organization.
2. Ask all of you to share more ways on how duplicates are created. How exactly associated attributes play a role? Modules? Teamwork?


Importing attributes via the managers

Importing elements (scott's diagram):

Thank you all ❤️

[Lingwisyer]

I have found the new Attribute Window a nightmare for keeping track of things since it lacks all of the Change Tab that the Attribute Manager has, but it is the only way to include folder heirachies... To add to your flow chart, if the name and index exist, but the attribute (composites at least) is different, it will just append it when set to import by name... I have had composites be duplicated multiple times when I accidentally import by name instead of index...

Ling.

[Stefan Videnov]

Hi,

I just tested what you said and I can't replicate it. The attribute just gets overwritten by name and no duplicate is created. The old buildup of the composite is deleted.

[Lingwisyer]

Odd... I will have to look more into it then as it has happened a few times recently... Might have to do with an iteraction with different modules.