Skip to main content
Antoine
Active Member
October 20, 2022

Nested property hidden with multiple selection

  • October 20, 2022
  • 104 replies
  • 5488 views

Been playing around with the “expose nested properties” feature currently in beta.
One of the great uses of variant properties is the ability to batch edit property values on multiple selected components. That use doesn’t carry over to exposed nested properties (yet I hope).

Demo file to help

When selecting one component instance exposing nested properties, said properties display fine. Add another instance of the same component to your selection (using Shift+Click), and the nested properties outright disappear from the right panel.

I haven’t seen this issue raised elsewhere! Do you experience it too?

104 replies

February 28, 2024

@y_toku
I think you’re missing the point, everyone here understands how to expose nested instances properties of ONE selected instance but what people are asking is to be able to see the nested properties when selecting MULTIPLE instances of the same component.

Jason_Leimgruber
February 28, 2024

came here from a search to find solution to this issue (which it seems does not exist yet).

commenting to keep this thread alive. this issues really nerfs the power of components.

y_toku
Figmate
Community Support
February 29, 2024

Thank you for pointing that out. It seems I had a misunderstanding. My apology for that. I now fully understand the situation and am currently discussing it with our team. I’ll share if I have more information to share with you.

Thanks again.

y_toku
Figmate
Community Support
February 29, 2024

Hi all,

Thanks for the feedback. I’ve checked with our internal team that it’s feature limitation due to some technical reasons. Exposed properties of nested components are not available when selecting multiple instances at the moment.

The post title previously included [LAUNCHED], which was incorrect. I have now removed it for clarity. I hope this clears up any confusion.

Your feedback is greatly appreciated and our product team will take it into consideration for potential future enhancements!

Thanks,
Toku

March 1, 2024

Hi @y_toku,

I appreciate the rapid feedback.
I think @dvaliao had touched on that point back in October, saying it would cause performance issues.
I think I’m not alone when I say please keep trying to implement this feature. It might not be part of any mainstream workflow but it would greatly simplify the kind of work that I use Figma for.

Thank you!

Kasia_Julia
New Participant
March 5, 2024

Well, not sure it’s that “non mainstream” I really think it makes workflow of people using complex design systems and using repetitive instances more tiresome. And I think this is often bigger companies case, which I would guess would be a good client for Figma. So maybe it should still be treated as thing to fix, even if technically difficult. Would be really a relieve to me, too : )

Kasia_Julia
New Participant
March 5, 2024

Also: this topic is still marked as “this topic has a solution” in the topics list. Can we remove that ; ) ? Because it’s not really true it’s solved : )

Karl_Martin
March 28, 2024

Bumping for a solution!

Araceli_Martinez
April 5, 2024

Commenting to keep this thread alive. We just rebuilt our library and now realizing this issue. I’m hoping we won’t need to wait any longer for Figma to add support for this.

Andrei_Armeanu
April 12, 2024

+1 on that. Come on Figma!