'Change to' with conditional action not working

Thought I was going crazy but then I found this topic, it’s sadly still buggy, won’t let me choose a different variant from the dropdown on a conditional, hope you guys will have a fix ready asap :S

Still experiencing this issue too 😦

Hi all,
Sorry for the trouble, and thank you all for flagging this!
After checking internally, the possible workaround that might help in the meantime, where you can create that connection manually before creating the conditional and then drag it into the conditional.

To be transparent, this bug might not have an immediate resolution. Due to its complexity and other priorities, it could take some time before we can address it. 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 understand how frustrating these types of issues can be, and we appreciate you bringing this to our attention.

Thank you for your understanding and patience while the team investigates!

Hi Celine,

I didn’t understand the workaround. 😦

me neither… is there any chance to make this work outside the main variable?

Hi all,
To give more clarification, the best way is to manually try and make the change to connection first by dragging out the connection arrow to the variant you want, then you can add in the conditional or other actions you want and click to drag the change to that section.
Here’s a GIF so you can better visualise it:

!!! Please note that this is a workaround that might help (« Change to » interaction on a nested variant /conditional statement). We are still currently investigating the issue. !!!

And, please also note that there may be some limitations and it might not help for every case. If this doesn’t work on your end, please fill out a ticket so we can investigate it further here: https://help.figma.com/hc/en-us/requests/new Thank you for your understanding! 🙏

Could we consider temporarily disabling the “change to” option in the “else” field of conditionals until a more satisfactory solution is provided? Currently, this feature seems to be causing frustration for many users, and the existing workaround feels quite hacky.

I’ve been dragging my feet about demonstrating the wonderful world of variables to my design coworkers due to potholes like these. I can’t in good conscience endorse a new feature if core aspects are frustratingly broken.

Any updates on the bug fix?

Agreed, I have waste hours trying to solve hoping that it’s been fixed.

It’s been 7 months, and the “after delay” issue that doesn’t work with conditionals to change a component’s variant persists.

That’s on top of dozens of other gaps and issues that force designers to spend hours or days coming up with hacks and workarounds to create BASIC site and app functionality and interactivity that could and should take a couple of minutes to set up.

One of the most determining factors of high-quality designs is the ability to quickly generate iterations. Figma has never facilitated that need up to this point (unless maybe for very basic designs with no interactivity).

I’ve been experimenting with other design software for the last 2 months. There’s one (I don’t know if I’m allowed to share its name here) that appears to be much better for prototyping. I actually think Figma copied its variables functionality from them.

Once I get the hang of it, I’m out, till Figma starts paying closer attention to designer needs.