Breaking parent-child relation in-situ, without "saving a copy as"

[schengnz]

The parent-child relationship can be very constraining. For example, it is not possible to insert two components that Fusion 360 recognize as clones (which is understood to have a parent-child relationship or have a common parent).

At the moment, if a component has a parent-child relationshop, the only way to break the relationship is by "save a copy as" on the child componnet.

Unfortunately this workaround is very troublesome. All other design which was previously using the old child component now have to be modified to use the new child component. Because Fusion does not allow for replacing component, it will involve a lot of re-design work if the child component had been used in an existing assembly.

It would be great time saver if it is possible to nullify parent-child relationship without creating a new copy of the child component. 

[promm]

The current experience is a result of the framework that is needed for future branching and merging functionality.  We understand that this is not the ideal workflow and are developing a solution.  I am accepting this idea because work is being done on the solution, however this is not a small project.

Cheers,

Mike Prom

[robduarte]

This seems like basic functionality that has been lost. We really need the ability to unlink components from each other. I'm surprised to see the "Make Independent" option just disappear with no apparent notification to users?

Rob