Component properties showing in the wrong order

Ask the community
1

Main component has the properties in order 1, 2, 3, 4, 5, 6

Instance of the component in another file properties are in a random order 1, 6, 5, 4, 2, 3

Any ideas how to fix? :bulb:

3 Likes
2

I have the same issue here.
reloading the file does not help. please fix this!

image
image616×782 23.9 KB

image
image486×438 16.2 KB

1 Like
3

Yes, same issue. However the title of the post is misleading since it’s the property values that are showing in the wrong order, not the properties themselves.

4

Hey everyone, thank you for flagging this! It does sound like the tool isn’t behaving the way we’d expect it and I understand the frustration!

This behaviour unfortunately seems to be related to a longstanding bug in Figma which can cause a discrepancy between the order of variant properties between the local (library) file and the imported copy of the component created in subscribed files.

I have noted these cases as an example in our open bug report for the issue but I also want to be transparent that this will not have an immediate resolution to reinforce the desired properties order and the team will require more time to fully investigate this. While I can’t promise a quick fix, please know that our engineering team is aware of the issue and will work towards finding a solution in the future. We appreciate your understanding and patience in this matter.

In the meantime, our team has suggested a potential workaround that may help resolve the issue. Could you please try the following steps?

  1. Go to main component sets with the issue, apply a small change to a property of the component. For example, like reordering the properties.
  2. Publish the change
  3. Go to a file with the issue, accept library updates and see if the issue is resolved
  4. Go back to the main component and reverse whatever test change was applied (reorder the properties back to the original order, do not use undo).

This method of pushing a controlled update in all of the dependent files usually gets instances back in a normal state moving forward. Can you confirmed if that resolved the issue or is the incorrect order still showing?

If you have any follow up questions or want to check on progress, let me know and I’m happy to assist.

6

This potential workaround is not working, no.

7

Hey @Marvin-aedifion, thank you for giving the workaround a try, and I’m sorry to hear it didn’t help. I’ll make sure to report this back to our team right away so we can look into it further.

I appreciate your patience as we work on this.