When I duplicate a page, or when I copy a master component, I want to have the option the “pasted” object to be a master component itself, or the duplicated page to be created with the same relationships between instances & components and to include master components as well.
Well, I think I found some solution how this can happen… When I have a master component in a page and I copy paste it into another file, it comes as an instance.
BUT when I have a master component AND an instance created from this component in the same page and I copy-paste them both together inside another file, then they come as Master component & instance, and not as 2 instances.
I have the exact same problem. This seems to be a bug. Only duplicating the entire file maintains the master and instance relationships… but that seems like quite a bother.
For some weird reason, this seems to affect mostly Master components without variants. Adding a variant to a component will make it duplicate across pages as expected, creating a new Master and not an instance.
This is a major issue whenever I need to keep a version history via pages with prototype links for each version. Any changes to the original master component can lead to changes in some instances on duplicated pages, which prevents me from keeping versions entirely within one file.
Hopefully Figma can address this and make it so that duplicated pages copy each master component, instance, and connection between them separate from the original page
When I duplicate a page, any master component on that page gets translated to an instance of the master component on the new page.
Is there a way to duplicate a page and create new master components on the new page? i.e. Page A has master component 1 and 2. When I duplicate Page A and create Page B, I want master component 3 and 4 rather than instances of component 1 and 2.
I realize I can detach the instance and create a new master component but for my use case, that is a lot of components to:
a) detach
b) make edits
c) re create new master components
d) go through each instance on the page and update it to use the new master component.
I’d rather:
a) make edits to new master components
b) have instances automagically reflect the changes.
I know this is an old topic but Figma hasn’t changed, and I just found this workaround by @Joanna6 :
It’s a slight variation on @Natasa 's solution above. Basically:
Duplicate file.
Create new page in original file.
Copy/paste all page contents from duplicate file back into new page in original file.
Delete duplicated file.
It’s a bit tedious but it’s still way better than recreating new main components and relinking all the instances of the duplicated page to the new main component, which is what I’ve been doing. I’ll now use this workaround to get the result I need.
I do something like this, which doesn’t necessitate creating a new document.
Use Component Master Manager plugin to move all existing components to a new page. You can choose which pages you want to pull components from.
I have found that it has not been updated to move components with variants, which kind of sucks, but I just cut and paste those to the new created components page as well.
Then, I duplicate the ‘Design R2’ page and create a ‘Design R3’ page.
Then, I use the Destroyer plugin to destroy all Instances and Styles on Design R2, so it becomes like an ‘archived’ version the client can have a link to. Meanwhile Design R3 is still connected to the original components, so I can keep editing away without messing up the now archived R2.
I have found that this preserves prototype links for the most part. A couple might drop off here and there.
I have the same issue, and the initial suggestion in this post didn’t work for me. I got an error when right clicking on a component instance and selecting “Go to Main Component”. Assuming it’s because I deleted the duplicated file.