'No' / 'Yes' variants, after being automatically converted to boolean, are still treated as string, stopping boolean variables binded to an instance from working

Hi @n_zrk, Thank you for reaching out regarding boolean property and string variables. We appreciate your insights and troubleshooting on this issue.

While I may not fully grasp your situation, I conducted a test on my end and was able to attach a string variable to the text layer nested within the instance that has a boolean property.

For more detailed information, you can refer to: Apply variables to designs

I hope this information proves helpful, but there’s a possibility that I may have overlooked something…
If that’s the case, could you please provide a brief video recording demonstrating the issue? Kindly show the full Figma screen, including the left and right panels, to display the exact names of the layers and properties. This visual aid will greatly assist the community in understanding the issue and enable us to replicate the behavior for further analysis.

If any members of our community have encountered a similar issue and have suggestions or workarounds, please do not hesitate to share them!

Thanks,

Hey @Junko3!

That’s not the case I was describing. Let me provide the video to be more clear.
If you create a component with variant values named No and Yes, Figma will automatically change it into a boolean toggle. You can attach a variable to this boolean, but Figma only allows to use boolean variable there while (this is my assumption) it still treats it as a string (No / Yes named variants). As a result attached boolean variable is not working. The example you provided is not using variants, it’s using a component boolean property which is a different case.

Hi @n_zrk, Thank you for pointing that out! I really appreciate you sharing helpful information and recording with us.

I tried it on my end and I was able to replicate the same issue where setting variant property values as [Yes] and [No] shows a boolean toggle for that instance property but doesn’t allow attaching boolean variables.

I think this behavior might be because the boolean variable value(True/False) doesn’t match the variant property values(Yes/No). For example, when setting variant property values as [True] and [False], you can attach boolean variables to the instance toggle.

However, I totally understand that this can be confusing. I have raised this concern internally and will update you as soon as I have more information.

Thank you for your assistance! If there’s anything else I may have missed, please feel free to let us know.
If anyone from our community has insights, please join the conversation!

Thank you,

Hey @Pradyumna1, as your question seems to be drifting a bit from the original post, I will create a new post right after this to assist you.

2 posts were split to a new topic: The applied variable appeared with a strikethrough

For anyone encountering this issue. Here is a workaround:
You can’t select a string variable but you can create one by clicking on this plus

I’m honestly very suprised that this bug still exists? Why am I not able to bind booleans to Component Names detected as a boolean?

I ran into the same issue, but my biggest problem is that I’m using a Toggle that’s coming from a Design System Library, so I can’t easily change it…. (I really don’t want to have to break the component or nest it in a new component just for prototyping...)

My Toggle component has 2 variants: “Status=On” & “Status=Off”.

Figma automagically converts this into a boolean, showing a boolean toggle. This was a cool feature when variants were introduced, showing a toggle when there was a variant with two options that were either “True”/“False”, “Yes”/“No” or  “On”/“Off”.

The problem: 
- “True”/“False”convert to a “real” Boolean
- “Yes”/“No” and  “On”/“Off” variants convert to a “fake” boolean 

Figma probably uses the same code/flag/tag to show a toggle AND to restrict which kind of variable you can apply, So it only lets you apply a boolean variable, but under the hood a boolean can only have “True”/“False” so it fails…

Screenshots:

This really needs to be fixed. Is there any way to give a status update, ​@Junko3 ?

Thank you @PaulUX for the workaround!