Copilot studio Condition node not working. Choice variable selection not saving

Question

Copilot studio Condition node not working. Choice variable selection not saving

Sibusiso 20

I am creating a topic which gives users information in copilot studio. I created a multiple choice question with a choice variable but the selection in the condition goes back to object Object after savings. Do you know what might be happening? Condition error choice not saving

Karan Shewale 2,505 Reputation points Microsoft External Staff

2025-05-21T07:18:36.67+00:00

Thanks for bringing this issue to our attention. We will check and update you soon.
Bernardo Martinez Romero 0 Reputation points

2025-06-03T10:28:09.7533333+00:00
Hi everyone,

Just wanted to jump in because I'm facing exactly the same issue and none of the proposed solutions worked for my case.

In my scenario, I'm using Copilot Studio to collect a multiple choice response and then pass it to Power Automate to run an external query. The problem is that Power Automate expects a string, and I couldn't get a usable one no matter how I tried to cast or transform the choice object.

What I tried:

Text(Topic.YourChoiceVariable) — gives me empty variable

Setting a new variable with Text() — doesn't help, variable remains empty

Referencing YourChoiceVariable``.Value — not valid in low-code

Using predefined string answers — no way to assign a stored value per option in the low-code interface

At this point I don’t even have a proper workaround.
Nothing I've tried gives me a clean string I can pass to Power Automate.

Really hope Microsoft introduces the ability to set custom stored values or exposes a simple .Value for choice variables in the low-code interface soon.

If someone has a working pattern to reliably extract the selected value as a string for Power Automate without Power Fx, I’d love to hear it.

Thanks!
sadiyhbvsofhuniuodfdwe 0 Reputation points

2025-06-13T07:26:36.3466667+00:00

The issue has been reported already in March 2025 in another thread: https://community.powerplatform.com/forums/thread/details/?threadid=a64b644f-0f04-f011-bae3-7c1e52171b3d)..)

So nobody has been able to create conditions based on a choice variable since then? What is happening Microsoft?

2 answers

Your answer

Karan Shewale 2,505 Reputation points Microsoft External Staff

2025-05-21T07:18:36.67+00:00

Thanks for bringing this issue to our attention. We will check and update you soon.
Bernardo Martinez Romero 0 Reputation points

2025-06-03T10:28:09.7533333+00:00

Hi everyone,

Just wanted to jump in because I'm facing exactly the same issue and none of the proposed solutions worked for my case.

In my scenario, I'm using Copilot Studio to collect a multiple choice response and then pass it to Power Automate to run an external query. The problem is that Power Automate expects a string, and I couldn't get a usable one no matter how I tried to cast or transform the choice object.

What I tried:

Text(Topic.YourChoiceVariable) — gives me empty variable

Setting a new variable with Text() — doesn't help, variable remains empty

Referencing YourChoiceVariable``.Value — not valid in low-code

Using predefined string answers — no way to assign a stored value per option in the low-code interface

At this point I don’t even have a proper workaround.
Nothing I've tried gives me a clean string I can pass to Power Automate.

Really hope Microsoft introduces the ability to set custom stored values or exposes a simple .Value for choice variables in the low-code interface soon.

If someone has a working pattern to reliably extract the selected value as a string for Power Automate without Power Fx, I’d love to hear it.

Thanks!
sadiyhbvsofhuniuodfdwe 0 Reputation points

2025-06-13T07:26:36.3466667+00:00

The issue has been reported already in March 2025 in another thread: https://community.powerplatform.com/forums/thread/details/?threadid=a64b644f-0f04-f011-bae3-7c1e52171b3d)..)

So nobody has been able to create conditions based on a choice variable since then? What is happening Microsoft?

Answer 1

Rich Conley 0

Any updates on this?

0 comments

Answer 2

Karan Shewale 2,505 Microsoft External Staff

Hi Sibusiso,

you can try this way to resolve this issue. The issue where a choice variable turns into [object Object] in a Condition node happens because the variable is stored as an object, not a plain string.

Fix: Convert to Text

To resolve it, cast the choice variable using Text() before the condition.

Option 1 – Inline Fix:

If(Text(Topic.YourChoiceVariable) = "Technical", ...)

Option 2 – Set a new variable first:

Set(ChoiceAsString, Text(Topic.YourChoiceVariable))

Then use ChoiceAsString in your condition.

Documents for reference:

Power Fx Functions - Text()

Copilot Studio Authoring Guide

Thanks,

Karan Shewale .

*************************************************************************

If the response is helpful, please click "Accept Answer" and upvote it. You can share your feedback via Microsoft Teams Developer Feedback link. Click here to escalate.

Peter Lindqvist 0 Reputation points

2025-05-22T08:34:08.8133333+00:00

I tried this approach, but the variable ChoiceAsString is always blank.
Karan Shewale 2,505 Reputation points Microsoft External Staff

2025-05-23T04:22:46.7266667+00:00
Hi Peter Lindqvist,

Thanks for getting back to me and for testing the suggested method.

If you're seeing a blank value in the ChoiceAsString variable, it’s likely due to when or where the variable is being set in your topic’s logic. Below are a few key things to review:

Suggested Fixes & Checks:

Place the Variable Assignment After the User Input
Ensure that the Set Variable node comes directly after the user makes a selection. If it’s placed earlier in the flow, the variable may not capture the user’s response correctly.

Use a Valid Power Fx Conversion
To convert the selected object to a string, try using:

Set(ChoiceAsString, Text(Topic.YourChoiceVariable))

Then, in your condition node, structure it like this:

If(ChoiceAsString = "Technical", ...)

Double-Check Variable Names
Confirm that the name you assign in the Set Variable node exactly matches what you use in the condition check—any mismatch will cause it to fail.

Inline Expression as an Option
If you're still running into trouble, try using the expression directly in your condition without a separate variable:

If(Text(Topic.YourChoiceVariable) = "Technical", ...)

Additional Resources:

Power Fx: Text Function

Using Conditions in Copilot Studio Topics

Variables in Copilot Studio Thanks, Karan Shewale ************************************************************************* If the response is helpful, please click "Accept Answer" and upvote it. You can share your feedback via Microsoft Teams Developer Feedback link. Click here to escalate.
MOREAU Sulivan 5 Reputation points

2025-05-27T16:29:40.33+00:00
Hello,

I'm experiencing the exact same issue with multiple choice questions in Copilot Studio.

In the low-code interface, I don’t have the option to define a custom stored value different from the displayed label for each choice.

As a result, the selected answer is stored as an object, and when I try to use a condition like: If Topic.MyVariable equals "Option X"

…the bot always takes the “other conditions” path or displays [object Object].

I’ve tried:

Using Text(Topic.MyVariable) → error: unrecognized identifier.

Displaying the variable → shows [object Object].

Creating an intermediate variable with Text(...) → blocked in the low-code interface, it won’t validate.

Conclusion: It seems impossible to compare a multiple choice response in the low-code interface without Power Fx support and without the ability to define a custom stored value.

Is there any official workaround or best practice to handle this in the current low-code environment?

Thanks in advance for your help!
Villada Moiron, Begoña 0 Reputation points

2025-07-16T11:27:23.3366667+00:00

Hello,

I'm also facing the same issue with storing the multiple choice question answer in a variable (of type choice or string) and using that variable value within a condition afterwards.

Interesting enough the topic containing this logic no longer gives errors (syntax errors), but the condition path (using the variable) does not get evaluated. (Same result as https://learn.microsoft.com/en-us/users/na/?userid=73828bd7-b823-4cc8-a987-7e8d829b6930 reported).

Are there other workarounds for this?

I appreciate any directions towards solving it.

Share via

Copilot studio Condition node not working. Choice variable selection not saving

What I tried:

2 answers

Your answer