Skip to main content
Question

Layer names are missing when updating instance

Ravil Shafikov

When I use an instance of a component in another component, to enable its settings in the right menu, I add display properties of the component instance. At this point, the settings group is named the same as the layer in the layers list. If I rename the layer, I will see in the right menu that the name of the property group has changed in the right menu. It works well as long as I'm inside the same file.

If I publish a component with such a renamed layer, then the first time I install it, I will see the correct display of the layer name. But as soon as I change the option in the child instance of the component, and then update the child component's wizard, the layer name resets to the initial one. This is only noticeable if the component instance has been modified. If we reset all the overlays, we will see the correct layer name again.

 

Video on Google Drive

Ravil Shafikov

Figma file with master component

Figma file with instance

 

djv
Figmate
  • djv
  • Community Support
  • May 16, 2025

Hi ​@Ravil Shafikov, thanks for reaching out! 

This is currently a known feature limitation for nested instance variable binding (NIVB). It’s noted under Nested instances here.

A nested instance does not transfer overrides if its variant is changed due to an attached variable changing values. This means that overrides do not transfer when a mode switch changes the variant of a nested instance. 

NIVBs can swap variants due to changes in the actual binding, the variable value, or mode context. Regardless of how this change happens, this can result in a different variant being swapped to and overrides not being transferred between variants. This behavior differs from normal nested instance variant swaps where a user explicitly changes a nested instance from one variant to another.
 
You'll only see this happen for variables which are bound to nested instances. As a workaround, we'd suggest either looking for ways to avoid this nesting to avoid overrides or to return to using component properties without the variable bindings where override preservation is needed.

 

We understand this is not ideal, but rest-assured, our engineers are looking for a way to support more consistent override handling for nested instances with variable bindings in the future.

Reply


Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings