Copilot Studio Variables Doesn't Show Up in {x}

(0) Share

Report

Posted on by YJ-02010636-0

In this topic, I cannot see all the variables initialized under the All other conditions node (e.g. can see Topic.Var1 but not Topic.Var2 when I click on {x}).

At the bottom of the condition on the left, it returns to "adaptive card" step so that user has to continue filling the adaptive card if everything is still blank. Adaptive card uses choicesets.

e.g.

{
    "type": "AdaptiveCard",
    "version": "1.5",
    "body": [
        {
            "type": "TextBlock",
            "text": "Select Ingredients for Your Formulation",
            "weight": "Bolder",
            "size": "Large"
        },
        {
            "type": "TextBlock",
            "text": "All fields are optional. Select chassis and ingredients to find similar studies.",
            "wrap": true,
            "size": "Small",
            "color": "Accent"
        },
        {
            "type": "Input.ChoiceSet",
            "id": "chassis",
            "label": "Chassis (Optional - Select one or more)",
            "isMultiSelect": true,
            "choices": [
                {
                    "title": "XXX",
                    "value": "XXX"
                },
                {
                    "title": "YYY",
                    "value": "YYY"
                },
                {
                    "title": "ZZZ",
                    "value": "ZZZ"
                }
            ]
        },
        {
            "type": "Input.ChoiceSet",
            "id": "ingredients",
            "label": "Ingredients (Optional - Select one or more)",
            "isMultiSelect": true,
            "style": "filtered",
            "choices": [
                {
                    "title": "XYZ",
                    "value": "XYZ"
                },
                {
                    "title": "ABC",
                    "value": "ABC"
                }
            ]
        }
    ],
    "actions": [
        {
            "type": "Action.Submit",
            "title": "Find Similar Studies"
        }
    ],
    "$schema": "https://adaptivecards.io/schemas/adaptive-card.json"
}

Categories:

Building Copilot Studio chatbots in Microsoft Teams

I have the same question (0)

All responses (3)

Answers (0)

Sort by

MichaelFP 2,001 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

If you Set Var2 before the condition it appear? Could be a logic issue, copilot studio could understand that will not pass to this branching and doesn't show up. Or could be because you did not set and the value for Var2 is blank and only accept string.

-----------------------------
If my answer helped you, please give me a thumbs up (👍).
If solve your question please mark as answer ✔️. This is help the community.
If you want talk with me just tag me @MichaelFP

Was this reply helpful? Yes No
Suggested answer

deepakmehta13a 369 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi,

This behavior usually occurs because the variable picker {x} in Copilot Studio only shows variables that are available in the current scope and have been explicitly created or assigned earlier in the topic.

In your case, the values from the Adaptive Card (such as chassis and ingredients) are defined as Adaptive Card input IDs, not automatically as topic variables. Because of that, they may not appear in the {x} selector even though the card is returning them in the submission payload.

To make them available as topic variables, you can explicitly assign them after the Adaptive Card step.

For example, add a Set variable step and map the submitted values:

Topic.chassis = turn.activity.value.chassis Topic.ingredients = turn.activity.value.ingredients

Once these values are stored in topic variables, they should appear in the {x} variable picker and can be used in conditions or other nodes in your topic.

Also note that variables created inside certain branches (for example inside a specific condition path) may not appear in other branches due to scope rules.

Hope this helps.

Was this reply helpful? Yes No
Pravishi Singh 8 on at

Like
a
(0)

Report
Copy link

Link copied!

This is a common issue in Microsoft Copilot Studio and is usually related to variable scope or initialization.

👉 Why variables don’t show in {x}:

The variable is not initialized earlier in the flow
It’s defined in a different scope (e.g., topic vs global)
The step is executed before the variable is set

👉 Quick fixes:

Make sure you set the variable first (use “Set variable value”)
Try changing it to Global variable, then switch back
Refresh or reopen the topic (sometimes UI sync issue)
👉 Tip: Variables in Copilot Studio are order- and scope-sensitive, so define them early and in the correct scope.

In short: initialize the variable first and check its scope—then it should appear in {x}.

Was this reply helpful? Yes No