Forking Derived Design & Its Uses

[zabelc554LH]

I'm wondering if someone could offer some advice as to the best practices for forking a group of related designs, so that the forked designs can evolve separately, while preserving the original designs.

I have a design (call it "Design_A") which from which components are inserted into other dependent designs ("Design_B" & "Design_C"), such that:

• Design_B --includes derive from--> Design_A
• Design_C --includes derive from--> Design_A 

I'd like to fork the whole series so that I have Design_A_new, Design_B_new, and Design_C_new: 

• Design_B_new --includes derive from--> Design_A_new
• Design_C_new --includes derive from--> Design_A_new 

Meanwhile, I'd still have the original Design_A, Design_B, & Design_C

What would be the best way of doing this within Fusion's versioning system (without having to fork Deign_A, and effectively recreate B & C)?

[TrippyLighting]

I don't think this can be accomplished within Fusion's versioning system. There isn't a copy with links available.

You can export the design as a .f3z and then re-upload it, preferably into a separate folder. However, you'll lose the version history.