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

April 16, 2024

Variables and components are still so far from good. We need simple fixes like this, not completely new under-baked features

Torjus_Berglid
April 24, 2024

I would like to be able to select several copies of a component and be able to adjust their nested instance properties, simultaneously. It’s possible to adjust the properties of multiple instances of a component, when these properties are “native” to the component. But we cannot interact with the nested instances properties. This means I in some cases have to turn on a nested instance property one product card at a time, which very tedious.

Antoine
AntoineAuthor
Active Member
April 24, 2024

Hi, duplicate of this thread.

Thanks

David_McEnroe
New Participant
April 29, 2024

Coming up against this in my build for tables and menus. Really bad experience for designers trying to bulk update anything with nested instances (like table columns)

Antoine
AntoineAuthor
Active Member
April 29, 2024

This thread and that one should be merged.

Ian_Palmgren
Active Member
May 6, 2024

Bump! Desperately need this. This is such a logical use case I had assumed I was doing something wrong with my file, and desperate googling brought me here. Frustrating ☹

@dvaliao can you remove the “solution” here, since this is not fixed and not a solve?

May 7, 2024

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

djv
Figmate
Community Support
May 7, 2024

Thanks, Ian! I removed the marked solution and merged the topics together, as suggested by Antoine.

But just to reiterate, the team is already aware of this feature request, but right now, allowing for this ability would cause major performance issues.

While it’s on their radar, they cannot prioritize it at this time. The team here will keep an eye on votes to gauge how this is affecting the overall community to hopefully vouch and make a better case for prioritization in the future.

Aaron_Xu
Active Member
May 10, 2024

+1. It’s very importance if I choose to organize my components with lots of nests.

May 24, 2024

Please fix this!