Clone Wars: Using multiple designs derived from one master file

[phazaar]

Okay, so on my current project I've ended up needing to split one master design file into several smaller section files in order to create a modular system. 

Before looking at the individual changes to make to each section, I've noticed it's impossible to put the pieces back together. Fusion 360 seems to have some kind of (surely nonsensically derived) issue where it won't allow you to put two designs into the same design if they both started out as the same file, REGARDLESS of how different they now are, or whether they share any components in common (they don't, in my case). 

I can't tell if I'm being foolish or if there's an obvious workaround, but this has completely killed my workflow here. Between this and the lack of variable parameters when patterning, I'm getting awfully worried I'll have to move back to Solidworks. 

Is there a fix coming down the pike? And in the mean time, has anyone got a work around beyond remaking each individual section of the original master file and wasting completely unnecessary amounts of my day? Is there some way to edit the file and tell it to forget it was ever copied from another file? Or to export it to a different file type and import it back in to make it forget? Anything really. If I have to model these parts again I may cry 😉

Thanks guys!

[TrippyLighting]

Could you perhaps create a screencast to show what it not working ?
It is difficult for me to just gather from your explanation what workflow exactly it is you want to apply.

[Phil.E · Accepted solution]

Actually we do not use nonsense to derive our solutions. 🙂

Initially I wanted to just say right click on a component and use Save Copy As. Then re-insert it. This is allowed. Very quickly I have several components on screen that are similar but distinct. Then I realized you must not be doing this workflow.

Can you list the steps in your workflow so I can offer a work around?

[phazaar]

Haha Phil, apologies for the poor english. Rather than derived from nonsense, I meant not sensibly derived - an oversight, rather than negligence or nonsense 😉 

It seems that's a good solution, though I can't understand why 'Save as a copy' has a different functionality with regards to duplication than simply... Copying... Anyway, I have done a quick run through of all of the parts, saved them all as copies of themselves, and cleansed the 'clones' from the system. All now works as expected, albeit with this one peculiar quirk, so thanks for the rescue! 🙂

[Phil.E]

The reason has to do with the style of Copy and how metadata is handled that identifies the models. We're working on it but it's rather complicated. 😞

Save copy as creates models without the issue.

Thanks for posting and glad to help!