my teammate found a temporary workaround for this.
Let’s say you have a page header or navigation containing links which you want to connect to different screens. But the original component and the screens are placed in different pages so they don’t appear in the interaction “On Click Navigate to” menu.
Also, you’re using component instances of the navigation in each screen.
Here’s what you can do:
Move the original navigation component to the same page where all screens are.
Place your interaction noodles and connect the nav links to the screens.
If you’ve connected everything, right-click the original nav component and select “Move to page” → select the desired page where it belongs to.
The connections should still be intact in the instances used in the screens.
“Move to page” is essential here, using cut and paste instead will not work.
Unfortunately, we could not reproduce it 100% of the time, sometimes even with this method the connections still got removed.
Consider trying it though.
So, it has been just over 2 years since this was originally posted and there is seriously no solution to this!? In that same amount of time, I’ve worked a few different contract jobs where the companies have bailed on Figma for this exact reason. We’d create larger prototypes to sell ideas through but to create larger scale prototypes, everything would have to be on the same Figma “Page” for all the prototype linking to work. But trying to add links to dev tickets became way too frustrating for devs to follow so devs would successfully lobby to dump Figma. If we could use Figma Pages as actual pages and then link between all the pages, this would make Figma WAAAAAAY easier to manage larger development projects.
I would love this feature. For larger projects, I would also love an easier to way to link to other prototypes as well. Right now we have to do an Open Link to get to one prototype to another but that forces opening a new tab in the browser and delays while you wait for the prototype to load. It does not look seamless when this happens which can be difficult if used for a wide audience demo.
Nearly 18 months since Figma support said it was “well aware of this need”. Nothing yet.
I know there are workarounds.
They are fine for a few screens on two or three pages but for a large project with hundreds of screens on multiple of pages they just aren’t practical.
Yeah I learnt that the hard way. Had a whole bunch of trickery with collapsible sub-menus only to realise there were (and still are) some pretty decent bugs preventing the prototypes from remembering the actual content of a menu after it was collapsed.