Referenced component disappearing when using 'get latest'

Referenced component disappearing when using 'get latest'

Roland.Kalamar
Contributor Contributor
521 Views
5 Replies
Message 1 of 6

Referenced component disappearing when using 'get latest'

Roland.Kalamar
Contributor
Contributor

I have a problem with a referenced assembly simply disappearing from my main assembly, when i try to use 'get latest' or 'get all latest'.

I was able to 'solve' this a few times with random retrying, resaving components etc., but now it really seems to start insisting on removing that component for no reason. I haven't even modified the part of the component that is used for the joint in the main assembly, or really any other part in a significant way.

Also, with these somewhat complicated referenced components, the whole thing is getting slow, though i don't know if it has anything to do with the referenced part not working.

 

Can anyone help me with this problem? It is one of those moments in Fusion that can be quite frustrating, honestly.

Thanks in advance!

 

0 Likes
522 Views
5 Replies
Replies (5)
Message 2 of 6

HughesTooling
Consultant
Consultant

At any point have you used Save As to make a copy of a design you've imported as a linked component\subassembly?

 

Mark

Mark Hughes
Owner, Hughes Tooling
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature


0 Likes
Message 3 of 6

Roland.Kalamar
Contributor
Contributor

Hi Mark,

 

I don't think it happened with the component that wanted to disappear. Some other components in the main assembly probably have save-as 'relatives' but i don't think these were created AFTER i inserted them in the main assembly.

 

BTW removing the component, then reinserting it (and applying basically the same joint again) solved it, at least temporarily (i used the get latest tool since that once and it didn't mess up the assembly). 

But i'm still extremely curious about what would cause such an error, as i suspect this could happen again later, if i keep using my working method.

0 Likes
Message 4 of 6

HughesTooling
Consultant
Consultant

The reason I asked about Save As to create a copy is because it creates an exact copy and all the object IDs are the same and if you import 2 copies into the same design it will cause conflicts.

 

One thing you could try is open the problem design and use Save Copy As, this will create a copy with unique IDs then delete the old copy from your design and insert the new copy. Make sure you use Delete not Remove. I had the same symptoms you describe in a design recently and had made the mistake of creating a copy of one design using Save As.

 

Mark

Mark Hughes
Owner, Hughes Tooling
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature


0 Likes
Message 5 of 6

HughesTooling
Consultant
Consultant

One more thought, are any of the inserted\linked designs assemblies that could contain linked parts that were created using Save As?

 

Mark

Mark Hughes
Owner, Hughes Tooling
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature


0 Likes
Message 6 of 6

Roland.Kalamar
Contributor
Contributor

Thank you very much for trying to help!

Maybe your guesses aren't too far off after all, as i see that i have multiple referenced components INSIDE the subassembly (that had the problem), which are exact copies, not even save-as relatives (meaning i dragged in the same thing twice from the left, i didn't know it could cause any problems).

So you are basically saying that i should never reference a design more than once, and also not use it along a save-as relative? But copies created with 'save copy as' are ok?

 

In this case problems seemed to occur only within the main assembly though, not when i was working on the subassembly itself.

0 Likes