Repository Issue with Extended Attributes

[Sean S]

We are experiencing an issue with the PowerDesigner Repository related to Extended Attributes, and before I log a case with Sybase, I thought I'd check to see if anyone else had experience with the same issue.

We use extended attributes with several metaclasses for a variety of reasons. We recently added a few new attributes to LogicalDiagram, and I have checked the Logical Data Model into the repository with these attributes populated.

Though I have double-checked via the Compare function that these attributes are populated in the repository, when the other architect with whom I'm working updates his model from the repository, the new attributes are not included.

He is able to add the attributes on his end, so I know he is properly hooked up to our extensions file.

If you have had similar experiences, or have an idea what we or PowerDesigner may be doing wrong, please let me know. We are currently use version 16.1.0.3637.

Thanks for reading!

Regards,
Sean

[Sean S]

I'm not precisely sure what the issue was, but we appear to have solved our problem. I removed the Extension from the Logical model on the other architect's copy of the model, saved, and then re-added it. I also pointed his copy of PowerDesigner to a User Profile that I'd previously created.

After that, the next time he updated from the repository, PD picked up the Extended Attribute changes. All is well again.

Sean