Nested property hidden with multiple selection

This feature is now out of beta, and this has still not been fixed. This makes all the work that the Figma team put into it pretty useless 😦 (for my purposes at least).

This really is a must. I have been underwhelmed with the number of use cases Nested instances helps with

+1 this is such an important fix for making nested properties actually useful

This would make the ‘nested component’-feature way more powerful and a hugh time saver. Please Figma 🙌

It looks like only the options for the final component show up when multiple instances are selected.
When multiple instances are selected, the user can press Enter until the properties for each nested component shows up, but its not a good work-flow.

+1 here. It makes batch editing a nightmare.

Yet another feature that just works as expected in Sketch. This gap makes for extremely slow work when editing data tables, long lists, etc. — and has made it onto my list of considerations for clients weighing software options.

This feature, along with being able to specify which nested fields are editable at the parent level (Expose nested instances -> at property level, also default behavior in Sketch), would significantly improve the experience of designing within your app, Figma.

+1 It would improve the usability of the design experience when altering multiple instances of components with nested properties.

The alternative isn’t very user friendly — I either:

1. Edit each components nested properties individually
2. Delete most of my components except for 1, modify the properties, duplicate the component, and re-apply any unique aspects such as data being used for text properties or image fills.

This would be a great improvement. I’m creating tables and need to select the component inside separately…

I agree this is a very frustrating and should be added natively.

There is however in the meantime a plugin called ‘Selection variants’ which automatically deep dives into all variants within a component and any components nested inside of it.

Its not ideal as it exposes everything, not just the properties you define at the top level, which means you have to look a bit harder within the plug-in window for the nested property you want to update.

It does work though and is better than manually updating one at a time.