Assign variables to variant properties of the main components & nested instances

Hey Friends,

I have created a plugin that can help with packaging components and component sets (variants) with variables, and enabling insert of such as component sets, components and instances with variables still attached to their source (global) or cloned as local variables.

Check it out at Figvar.com or just search for the Figvar plugin.

Cheers,
Martyn

Please support assigning a variable to an exposed property in a component. In Microsoft, components are heavily used in design deliveries between disciplines. An example would be from UX to CX (Writer). Being able to assign a variable to an exposed property in a component, especially when multiple instances are used, dramatically reduces the amount of laborious work to manually update all the instances.

I see that similar requests have been submitted as early as 2022. I was wondering the reason this is not supported. Thank you!

Wasn’t this obvious from the start?!!! It’s been more than 1 year since variables are released and this MUST HAVE feature isn’t available yet? How can it be? And all we get is new UI, which btw makes it harder to access basic features. :///

Agree there – how can it be that a UX/UI tool has bad UX? 🤦‍♂️ is getting worse with each update, not to mention not able to adjust the UI’s scale? I have a 27 inches monitor and still struggle to read the absurdly small font on the Inspector!

+1 for this feature, I use nested components all the time and don’t want to break the dependency

Keeping this idea alive +1

+1 for this feature

Yes +1.  So many limitations with nested variables :(

Would really love this. I don't understand why this hasn't been in any of the releases over the past years, as it seems like a very obvious feature that makes variables actually useful. Instead, we get all these beta products that nobody asked for.

It’s my most wanted feature right now