Nested property hidden with multiple selection

Bump.
If performance is a concern, is it possible to mitigate that by making the nested properties visible only if the number of selection is below a limit?

Similar to this auto-spacing function that currently has an upper limit for selection, beyond which it’s not available / disappears.

+1 This is quite annoying to deal with

Hello again,

I stumbled upon a weird scenario when setting up the different variants in a design system of a component in an example overview. I use nested components to control the size and potential styling so that you don’t have to create multiple variants with the same structure when all you need are different variant states.

For example, an input field has a label, a field area (where there can be an icon, placeholder, and so on), a help text, and an error text. However, we also need to see the different states of the input field, which means Default, Hover, Disabled, Active, In use, Focused, and potentially, for prototyping, we also need Active Hover and Active Disabled.

All of this takes time to set up, but when I want to create an overview of the different examples and display the prototype effects, I have to manually select them all if I want to change the size from Medium to Large, for example. Because my nested options disappear as soon as I choose them all, duplicate, and wish only to adjust the size.

This is a time-waster, so it would be nice to display them instead of hiding them. Please, please, please show the nested properties as well! I’m begging here!

Best regards,
Morten.

+1 Bumping this to keep it relevant

Same issue here. Doing file refactors at the moment, and being able to edit the nested instances of multiple selections of the same component would speed things up considerably!

+1 this is key for working with nested instances. Can’t use it without the ability to edit multiple selections for my use cases (tables).

+1 This is must have should be fixed. Otherwise it’s just a partial feature not aligned with actual workflow.

This has been an issue for 2 years now … do we have any updates on a fix?

+1! work can become quite tedious without this feature! please Figma 🙏

I’m sure everyone has the same idea - keeping the thread alive until Figma can make the fix. It’s been over 2 years with this issue. We have multiple clients within our agency firm and deal with both our own internal design system as well as client design systems.

It’s a large pain point for my team and myself to individually select components that share the same nested properties and not have the option to bulk select/use the nested options. Hoping that Figma’s team places this into a sprint for fixing.