Accept library updates per page

@Anne13 Unfortunately it does not. I appreciate you trying to clarify but I’ve reread the article.

Something’s off somewhere on Figma’s end. It’s either a glitch or a misalignment on their end between what the feature is doing and what they THINK it’s doing.

@Junko3 @Anne13 I just confirmed with Figma support directly that what we’re describing, Anne, should NOT be happening. I would get in touch with someone who can escalate this for you.

Hello @Anne13, Thank you for clarifying and I apologize for the misunderstanding of the issue.
Also, I completely understand that it can be a bit confusing when selecting “Update all” in the “Current page” tab results in updating instances of the asset on other pages as well.

For the visibility, I see the case of @Kevin_Zazzali on our backend about this, and we are currently investigating this further.

Thank you for your help and cooperation!

Thanks a lot for your replies and for passing this on to the team.

I have also heard from designers at other companies that branching (which is part of the Organization plan, we don’t have that) could offer a solution to my issue of freezing “ready for dev” files while still being able to work on and accept updates for other parts of the same file… something to look into.

Hello there! I just want to share key points from support with the community for visibility.

Currently, the functionality you are experiencing when selecting “Update All” while viewing the Current Page tab from the update modal is expected. It will update all instances across all pages of the file.

We understand that our help center article may have caused some confusion, and we have revised it to better align with the intended functionality.

Thank you for taking the time to share your feedback on this feature. While we can’t make any promises, our product team is already aware of this!

We truly appreciate your input!

Hi, I have the same problem; it is very inconvenient to update components since I cannot do this page by page. I have a trick, and maybe it will be helpful until Figma figures out how to fix this issue.

1. I create a new Figma file and attach the necessary design system to it.
2. Then, I copy the screens that need to be updated and paste them into the new file.
3. I update the components in this new file.
4. Copy updated screens, and move them back to the original file.
    

Currently, the functionality you are experiencing when selecting “Update All” while viewing the Current Page tab from the update modal is expected. It will update all instances across all pages of the file.

​@Junko3  If this is the “expected behavior” I think the community is telling you that the design is not reflecting that behavior nor is the expected behavior how we want it to work

1. We are saying that when we see in the flow of applying updates “Current page” it is indicating to us that the update will only apply to the current page and no others. If the expected behavior is that it will apply on all pages, than the Figma UI needs a better UX design.
2. We prefer Figma leap frog and instead make it work differently by actually allowing us to apply updates per page. Here is my use case:

I work on ideas on a page. I review them. I copy the page to preserve the review, renaming the pages. I don’t use version or branching, as this helps preserve the review history, keeping the reviews visible and easy for stakeholders to see the rounds of feedback. I do this enough times I may have 5-10 pages. I’m about to work on another set of changes and now I need to update a global component. But if I do, I only want it to updates on the most recent page and preserve the iterations as they were designed on those pages.

Today, this is only possible if I 

1. copy the file and start over
2. copy the page, name my version, and detach all nested components on previous pages
3. knew to use a wrapper component around global components from the beginning. then i could have duplicated that component, detatched global component from first wrapper, then updated  the global component in the new wrapper, then used new wrapper moving forward - but I can’t go back in time nor do I want to have to know to do this upfront.

It’s crazy that this hasn’t been fixed yet. I now have to create tons of separate Figma files to have reliable documentation of what designs looked like in the past, which is really messy. Frustrating for myself and PMs and creates lots of confusion. 

Please just allow us to accept updates from a library and apply them on individual pages. 

Updating the components that appear on one page, but then apply the changes to those components across all pages is weird and unintuitive. 

I found a workaround!  While the way I expected this to work is to apply an update per page (so please Figma still prioritize this), I found a way to do this with existing functionality.  Inspiration hit when I realize how I was doing this within a file, then I simply applied this method at the library level:

Within a file:

1. ​Create component to reuse within that file to speed up ideations and mock faster. Will consider adding to pattern library or design system later once we know this is what we want to use.
2. Copy pages to track feedback loops and keep iterating.
3. Want to update a component, but not affect the rest of my pages to preserve old idea…
4. Copy component, rename existing to “[previous name] V1” or something
5. In latest page, swap to new component. Done!

To abstract this to library level:

1. Put component and any nested ones into a section called “[previous name] V1”
2. Duplicate section and Rename
3. Rename all old components with “v1”
4. Old mockups using this component still reference the original component
5. Publish new component
6. Go back to your file and accept update
7. Switch to using new component in latest page.

What’s nice about this is I now also have a history in the library file of how tha component evolved over time too.