Power Automate

Form Broken once shared with Teams

(1) Share

Report

Posted on by JS-22051149-0

I recently created a form and tested the flows just fine.

However now that its shared to a Teams page suddently its not function correctly now.

Note previously the link had been shared via URL to which it worked fine

The first major issue is with my switch

This is the error

The execution of template action 'Additional_Day_for_Severity_Values' failed: The result of the evaluation of 'scope' action expression '@outputs('Get_response_details')?['body/r55ab857b1a2947669e82e63d3219427d']' is not valid. It is of type 'Null' but is expected to be a value of type 'String, Integer'

This doesn't make sense to me personally as the value is one of a multiple choice that has to be seleceted so the value can't be null

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (0)

Sort by

JS-22051149-0 24 on at

Like
a
(1)

Report
Copy link

Link copied!

The first major issue is with my switch

This is the error

The execution of template action 'Additional_Day_for_Severity_Values' failed: The result of the evaluation of 'scope' action expression '@outputs('Get_response_details')?['body/r55ab857b1a2947669e82e63d3219427d']' is not valid. It is of type 'Null' but is expected to be a value of type 'String, Integer'

This doesn't make sense to me personally as the value is one of a multiple choice that has to be seleceted so the value can't be null

Was this reply helpful? Yes No
Suggested answer

Valantis 6,735 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @JS-22051149-0,

The null value is almost certainly because the question ID in your flow no longer matches the actual question in the form.

When a Microsoft Form is shared to Teams as a tab, it sometimes creates a copy or a linked version of the form. If the flow was built against the original form, the internal question IDs (like r55ab857b1a2947669e82e63d3219427d) may not match the version now being submitted through Teams.

Check two things:

1. Open the flow and look at the Forms trigger and Get response details action. Verify they're pointing to the correct form. If Teams created a copy, the flow might be reading from the wrong form and getting null because the question doesn't exist on that version.

2. The Switch action is using a hardcoded question ID. If that question was modified, deleted and re-added, or if the form was duplicated, the ID changes. Go into the flow editor, click on the expression and re-select the question from the dynamic content picker instead of relying on the hardcoded ID.

The fact it worked via URL and broke when shared to Teams strongly suggests two different form instances are involved.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
Kalathiya 2,456 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @JS-22051149-0,

Automation is getting the failed due to "@outputs('Get_response_details')?['body/r55ab857b1a2947669e82e63d3219427d']" field value getting null.

Could you please explain what you are doing in this "Additional_Day_for_Severity_Value" action? that will help me us to guide proper solution.

Was this reply helpful? Yes No
Suggested answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!
Since:

The flow worked previously.

The issue started after sharing through Teams.

The question is required.

The most likely causes are:

The Teams tab is referencing a different form instance.

The internal Forms question ID changed after edits to the form.

The dynamic content in the flow is stale and needs to be refreshed.

Next Step

Go to the failed flow run and inspect the Get response details output. If you can see the JSON returned by that action, it will immediately show whether:

The field is missing.

The field is null.

The flow is reading the wrong question ID.

That will pinpoint the root cause very quickly.

Was this reply helpful? Yes No