Allow assigning String variables to Text props in component instances

Please for the love of god let us assign variables to text elements nested in components. For example, I’m using Material 3 Design Kit. All text fields are built out with all kinds of great switches and knobs allowing me to control switching variants and properties using variables, saving a lot of time not having to manually do it or create additional screens. But if I need to say, have the same mock value show up in a field in one place, then it appears somewhere else, and also propogates between different variants of either of those elements, I have to detach the entire component, recreate all those variants locally and assign a string variable, because a lot of times, when a variant is changed via an interaction, the text will reset to the base text for the component in that state (say going from Enabled to Hovered, which is SO frustrating. Basically, it defeats the purpose of having variants at all. I might as well just create them all myself from the start. Yeah it’s a great base to work off of, but what’s the point of having a shared library between teammates if we all end up making local versions in our design files that, over time, because further and further away from consistent because they are not pointing back to the core library of components? Seems so basic. I mean, many UIs are forms, or require some sort of manual entry of values from URL addresses, to IDs, to names, dates… like, I could create a dynamic mockup of a list of 5 items that starts with none, but as a user “enters” values into the text fields and submits them, they could “create” a new list item with that name… it seems so obvious - like how is text/strings/inputs the last variable type to gain functional support? I can’t believe this has been a thread from over a year ago and there’s still no new news about the capability.

Seriously, this reads like a bug report from the twilight zone (just keeping the thread open).

This was the first thing I tried doing with my components, and the fact that it was borked like this left my jaw on the ground.

+1 for this ‘feature’.

The docs say that you can apply a string variable on any text layer, which is not true, as you can not apply it on a text layer that is connected to a text property 😦

This feature would be much appreciated!

Is there any update on this topic?
Thought in UI3 this might be fixed, but no.

October 2024, new UI is everywhere… But no solution to this issue 😭

I was exactly looking for this! I was thinking I might’ve missed it, but I am sad to find out you can not combine text properties and text variables 😅

We are using a component library that we don’t have access to edit. So we can’t remove the button’s text property to assign a translation variable to it (which by the way is already crazy that we have to do this).
This is extremely inconvenient and frustrating for us. 😩

I still need this as well.

Yeah it’s wild to me that I have to detach a component to be able to create a simple drop down menu that allows the user to select one of three options. Like Figma really thinks we are only using it to create slideshows apparently. I’m going to keep responding to this every 2 months to keep the thread open until they figure this out.