Announcements
Autodesk Community will be read-only between April 26 and April 27 as we complete essential maintenance. We will remove this banner once completed. Thanks for your understanding

"Get Latest" after updating appearance on linked file deletes several components

Anonymous
393 Views
2 Replies
Message 1 of 3

"Get Latest" after updating appearance on linked file deletes several components

Anonymous
Not applicable

Hi all,

I have a design where I started with a linked component, and referenced that component to make several new components.

I went and opened the linked component file, updated its appearance, and saved it, and pressed "Get Latest" after doing so, and it seems to have completely broken the file I was using the linked component in. Most of the new components I have made have disappeared from the Feature Tree. All of my features in my design history, though, are still there, though they are missing references:

Before "Get Latest" and after "Get Latest", and a random joint from the intact Design History missing all of its references.
Before "Get Latest"Before "Get Latest"After "Get Latest". Note most of the components are now gone, but the design history is intact.After "Get Latest". Note most of the components are now gone, but the design history is intact.A random joint from the design histroy. It's missing all of its references.A random joint from the design histroy. It's missing all of its references.

I pressed "remove appearance override" on the linked component file to return the appearance to its original state, and saved it. It still causes the design to break when I press "get latest".

I promoted an older version of the linked component file, and even after I do this the same issue occurs.

Is this is a bug, or am I doing something wrong? Thanks!

Reply
Reply
0 Likes
Accepted solutions (1)
394 Views
2 Replies
Replies (2)
Message 2 of 3

Anonymous
Not applicable

So I noticed that all the components that get deleted are independent linked components.


I can "Get Latest" on other components without issue.


Also, if I try to "Break Link" on the component that breaks the assembly, it says that it will be aborted due to the cyclic dependency error.

Reply
Reply
0 Likes
Message 3 of 3

Anonymous
Not applicable
Accepted solution

Apparently "Compute All" also breaks the assembly, and said that there was a sketch that was causing a circular dependency on another sketch. After deleting the offending sketch everything works fine.

Reply
Reply
0 Likes