Same here :S we need that! :S
I was just about to approve using String Variables for translations - it worked great especially since we translate designs in reverse. For some time I thought it was just a bug that some strings connect to variables, and when you unfocus them, they lose the variable. Now I see that it’s a missing feature. I agree, that without it, this feature is unreliable and unusable in a scalable way.
4 Likes
Assign variables to variant properties of the main components & nested instances - #5 by Armin_Rouhanian found a similar topic
Hey everyone, had the same issue, wrote a plugin for it, hope this helps ! https://www.figma.com/community/plugin/1283084251253914878/apply-string-variable-to-prop
And that this shameless auto promo is not frowned upon !
4 Likes
Now that variables are available for nested instances I was excited to use a variable on a (nested instance) text property, but just realized you can’t. Sadface…
4 Likes
Barmp. Just came across this for the first time and thought I was missing something obvious. Hope the Figma team can get this shipped soon 
1 Like
We really need this!
1 Like
This seems to do the job as a workaround, thanks! 
Hello! I would love to see this too. Especially because I use the Relay plugin from Google and it only supports component with properties, so now I need to have two components, one for the design and a clone of it for Relay
Almost a year later, but this is still not implemented 
1 Like
This stops me from using text variables seriously
1 Like
Let’s go Figma team! Lot’s of great reasons to ship this feature 
5 Likes
I found a bug(?) and potential work around for this until we get this feature in place. 
If you only select more than one text element the variable button appears, and allows you to connect a string variable to a text in a component with text property. But the text property will not be connected, only overwritten. 
7 Likes
<Nearly 12 months later> How can this not be implemented already?
Death by a thousand cuts!
2 Likes
OMG! Thnk you very much for this crazy way! Awesome! )))))))))))))
1 Like
This shouldn’t work, but it does! hahaha 
Also to add to this, I only find that this works if you use two different variants of the same component
1 Like
Yeah I just noticed this too, thought it was a bug that you COULDN’T assign it to a single instance which is how I found this thread! Guess it’s the other way around
One thing to note with this workaround though - if you have any interactions tied to an instance the variable won’t flow through while prototyping (i.e. hover states), or at least that’s what’s happening to me!
1 Like
Yeah don’t think this work-around works anymore…
Without this text props are useless to me. To use the translation variables collection we have created, I have to go into every component, remove all the text props, and then attach the string variable.
Please Figma - implement this
1 Like
Posting to say I also need this feature too, and to keep the issue from closing. I’d like to add the text prop on the parent component for a “county” name and have the prop propagate to multiple “fields” within the component (county@domain.com, County Website, etc.)