Some prototype connections lost when copying page

Description of the problem

  1. I have a set of frames with prototype connections on a page
  2. When copying that page, some of the prototype connections break. Not all of them, but some. It seems more likely to break overlays than navigation.

Does anyone else experience this issue? If so, have you found a work around?

I’m working with a high volume of prototypes that are copied and locked for sharing with clients. That way I can keep iterating on the main one and they have access to a snapshot of the prototype from our last review. Having to go through every copy I make in order to repair these links is tedious and time consuming.

3 Likes

Maybe you have components on your page? They are copied as instances when duplicating the page so it’s not possible to keep their connections.

1 Like

Hmm that’s a good suggestion and I will definitely keep an eye out for that in the future, but I keep all my main source components in a different file and import the library. All of the components on the prototyped pages are instances.

1 Like

Experienced the same issue. If you’re copying it within the same file but just to a different page, then try duplicating that page and deleting everything apart from the content that you wanted to copy. This way it retains the links.

1 Like

Copying entire pages has been my standard practice, but this issue still persists. Since my original post, I’ve even run into issues where prototype connections are lost within files I haven’t even opened since originally creating and successfully testing those connections. Overall it creates a very unstable experience, especially when sharing prototypes with clients.

I’ve been getting the same issue. Doesn’t matter if components are on the page being copied or elsewhere, loads of links just disappear. I need to copy the whole page with its prototype intact.

(I also contacted support about it)

1 Like

The issue is that if your master is made of variants and you update those variants incorrectly, like I did, the instance looses its link. When updating the variants do not delete any of them but apply your updates to each one individually (best practice they should all derive from the top variant so you alter only one).

What I did instead - I deleted one variant then duplicated the one above which already had the updates, then renamed it to the same name, however to Figma this is a different components since the component ID is new (we don’t see this but ideally Figma should allow us to overwrite them somehow)

Then you need to go back to your instance and replace it by typing the same name and selecting it from the list. Now it is linked to the new variant even thought name has not changed.

Regarding your issues I have always dragged and duplicated pages and instances and never had problem with lost links.

If you need more help contact me www.ConciseUX.co.uk

The bigger issue when you have extinct components in the Assets search results. You cant drag them in. The process of restring them is long. Figma should allow right-mouse (RM) click replace with… or RM locate on canvas (many times these are old components from dead libraries so they show as “used in this file”) Ideally Figma should give options to only display results from my switched on libraries, and hide what’s on the canvas or Local components. or at least list them in sections so we know what to ignore.

If you need more help contact me www.ConciseUX.co.uk

Really hope Figma’s looking into this issue! I have the same issue all the time.

I am also having this same issue. Please look into this and fix ASAP. To be specific, the major issue for me is the connectors work so well in Figjam to show the flow of my wireframes. The plugins for Figma just do not work as smoothly in Figma. One aspect is that I am able to move the connectors to subtle spots that I cannot do in Figma. However, I can no longer take the risk of moving symbols from Figma to Figjam and back because they break. Thank you.

I have the same problem even when I duplicate pages

I’m having the same problem;

  • I copy-paste a prototype on the same page. In this case outgoing connections from a component are wrong (in the copied prototype, this component becomes an instance and takes its outgoing connections from the component, so it is connected to frames in the original prototype rather than the copied one). I guess this is expected behavior and easy enough to prevent. (Weirdly, incoming connections are copied correctly.)
  • I copy-paste a prototype to another page or I duplicate a page containing a prototype. In this case many more connections are lost and I cannot determine why those are lost while others stay intact. This is problematic and seems like it’s a bug.
2 Likes

This seems to be happening to me only for conditional interactions.

I’m having the same issue. Mainly, the conections lost are between pages.

Duplicating the page instead of copying solves it, but then creates another problem: Several components lost their customized text, returning to their component text (e.g. all buttons return to the “button” label I placed at the component)

Found a soluion! To ensure that all links are imported to the duplicated page, you need to make sure that the main component (the one you drag links from) has at least one variant before duplicating the page.

If the component only has a single instance with links, those links will not be imported to the duplicated page.