Nested instances reset to default when applying parent modifications like booleans

[Sasch]

Hi, I’m facing a strange behaviour right now and I did not find a way to make it work yet…Maybe you folks can help me find a solution or point me in the right direction.

My plan is to create a sidebar navigation pattern where designers can modify the menu structure easily.

The structure of the example includes a “Single Item” component set where all the different navigation link type are collected (e.g. Headline, Link, Subline, Divider, etc.) and a “Section” component set that is used to allow the designers to choose how many navigation items they want to have in a section.

Now to the strange behaviour. When I use the “Mobile” boolean on the “Single Item” component all works as expected. Inactive “Mobile” is full width and active “Mobile” is max-width of 68px. See an example below:

Now when I apply the same settings to a “Section” component only the unchanged link types have the custom text I applied earlier. All link items that have been modified are overwritten by their default state. What I would expect is the “Headline” and “Subline” to have the modified text like in version where mobile is not active. See an example below:

It’s strange to me that, for example, the nested instance is still remembering that I changed it to a “Headline” type but not remembering the text I entered. This way its impossible to allow the designers to easily change the sidebar to collapsed without changing the content for the mobile version manually. What am I missing here?

Here is a sample file to see the behaviour in action:
custom_override_bug.fig (84.6 KB)

[Gayani_S]

Hey Sascha, I’ve checked internally and got the confirmation that this is not an expected behaviour. Please reach out to our support team, they can investigate further and file a bug report on your behalf.

[DeniseN]

My team and I are also experiencing this issue, was a solution ever found?

[Sasch]

Nope but I was too busy to reach out to the support team…we still have this issue.

[Gayani_S]

Hey @Sasch, sorry to hear that you’re still experiencing the issue.
I’ve just created a support ticket on your behalf. Your ticket number is #1002446, for reference.
Our support team usually takes up to 24 hours to reply back to emails - tends to be quicker than that in normal circumstances. However, please be aware that we are facing increased contact volume so there might be a delay

Appreciate your patience in the meantime!

[Gayani_S]

Hey @DeniseN, I am happy to have an eye on the ticket from the user when it’s being processed by our Support team to give you more information about it.

Alternatively you can reach out to the support team directly via this form: ​https://help.figma.com/hc/en-us/requests/new?ticket_form_id=360001731233.
Please also share your file link with our team and invite support-share@figma.com directly as an editor (this won’t affect your billing at all).

Thanks!

[Sasch]

Hi @Gayani_S thank you for creating the support ticket I will let you know in here if it was a bug, if yes how we fixed it or if I was just using a wrong approach.

[Gayani_S]

Hey @DeniseN, wanted to give you a current update on the ticket.

Our engineering team have been investigating this issue and to be transparent this will not have an immediate resolution as they need more time to investigate this and fix it due to its complexity within our override logic.

We can’t promise a quick fix, and please know that our engineering team is aware of the issue and will work towards finding a solution in the future.

Please let me know if you have any further questions.

[JustJest]

I am also experiencing this issue. @Gayani_S I know you said that you cannot promise a quick fix but is this bug currently in the queue to be investigated and worked on. There seem to be a fair number of issues related to this on the forums. Just a few I have found.

Updating component library does not push change in component instance where there is nested/hidden components, forcing me to "reset all changes" route

This has happened in multiple components of my library and design files but I’ve just not bothered with it and manually updated it to this point. We are introducing a large change in UI and I do not want this to happen as we scale more down the road. Our library has nested and hidden master components within one master component to be accessed by our designers. Example: “_item/ Single Tab” which has 5 variants for states and multiple boolean options for that single tab. [Screenshot 2023-10…

Nested variant instances within a component are reset after the library update?

Hello everyone 1 year later, I think I’m experiencing exactly the same issues as those mentioned in these topics: Unfortunately, the solution suggested in the related topics I mentioned above — reload Figma and run “Fix instance overrides” from the Quick Actions — is outdated and no longer exists. If there a new solution? if I may summarise the issue: When we nest a variant instance within a component, use that component in another file and select a different variant va…

Nested component properties reset when updating parent component

Hi there. Here is my case: In a library file I have a data cell component to represent table data. It is basically an autolayout frame with three parts: left, middle and right. Each part is a reference to a set of components (ex. datacell/middle/comp1 and datacell/middle/comp2) and has an instance swap property. With this set up I can add a data cell and choose each part to output different types of data. I guess this solution it is a common one. In a design file I have lots of tables with d…

Bug report: updating the table component wiped all values

Hi all, I wanted to submit a bug report to the team that had me lose about a week’s worth of work. I’m using a set of components produced by the Polaris team, they updated the table component and it wiped all the values from all of my tables. I’m not sure what could be done to fix this, but from now on I will not be updating components with customized data in them, which makes that entire feature less customer usable. Thank you for your time.

Nested components defaulting to standard property settings after parent component changes variant

I have made a side menu that contains several layers of nested components. The issue is that when i enter preview mode some of the properties of some of the nested components (but not all) revert back to default whenever the parent component changes variant. Problems include: Icons that have been swapped using instance swap property reverting back to default. States (Active/Inactive) reverting back to default Hidden elements reverting back to default. I.e. will be shown again Text properties …

Inconsistent behavior when updating a file with component changes

When I release changes to the design system library file, the update behaves inconsistently and I can’t reliably predict how the update will impact my team. Sometimes text will be completely cleared and reset to the default text found in the original component, while other times the text will remain intact. Sometimes a component will not update at all even though I have selected to update everything. Instead, I will see the blue sync icon and have to update that component individually, but I w…

Also, where is the Fix Instance Overrides command that this thread is talking about?

Recap of the override bug that occurred on 01/20

Sorry for the confusion & oversight, @Enes_K @nijnooy! As Jessica mentioned, the fixes we described above handle the vast majority of cases, but there are still a couple of perfect storms that can occur with the right timing of various actions like publish, update, override, reload, nest, swap, publish again, override again, restore version, etc. The forums are primarily run by the community, and our support team is working on more sophisticated tooling to help remediate any edge cases not add…

[Gayani_S]

Hey @JustJest, thank you for reaching out and also collecting these issues!

I’ve went through these post and I am seeing slightly differences in the issues. Could you explain what you’ve been experiencing? It would be best to have a screen recording, so I have a better understanding.

Thanks in advance!

[Ivan_Perez]

I don’t know if this error is related but what happens to me is that i have nested instances inside other components and whenever i update some property on an instance it resets every property of the component, I don’t know if I have designed wrong the component and I don’t know how to solve it, it’s driving me crazy.

[Francisco_Caballero]

To prevent issues with the Prototype and Components with different variants (states like collaped=true/false for instance), each layer must have its name since it will be used as class names during the transitions.

Keep a clean naming convention, and be sure that nesting is properly defined.