Unanswered

Error when using select in Manaul trigger

(0) Share

Report

Posted on by Jojo222813

Hi All, I have a question about using select in Manual Trigger Flow. I am not sure which part cause the error. Please help me!!

I have created a Manual trigger flow. The flow is working when I remove the 'Select' part. If I add 'Select', it always show "The input body for trigger 'manual' of type 'Request' did not match its schema definition. Error details: 'Invalid type. Expected String but got Null.,Invalid type. Expected String but got Null.'." when I click "Run Flow".

Any one have ideas about this case?

Categories:

Building flows

I have the same question (0)

All responses (10)

Answers (0)

Rhiassuring 8,690 Moderator on at

Like (0)

Report

Can we please see what your Get Items and Select actions look like?

Thanks! 🙂

R

Was this reply helpful? Yes No
Jojo222813 64 on at

Like (0)

Report

Hi @Rhiassuring ,

Here is the Get Items Action:

Here is the Select action:

Was this reply helpful? Yes No
Rhiassuring 8,690 Moderator on at

Like (0)

Report

Thanks! Do you have a field called "Title" on your manual input form? Is it your intent to pull "Title" from the manual input form into the Select, or, are you looking to get the Title from the SharePoint items you have retrieved?

Was this reply helpful? Yes No
Jojo222813 64 on at

Like (0)

Report

I am looking to select the 'Title' value from my share point list.

Was this reply helpful? Yes No
v-yujincui-msft on at

Like (1)

Report

Hi @Jojo222813 ,

Based on your Screenshots, i created a flow similar to yours, but it worked fine on my side.

Maybe you could try create a new flow, sometimes it will solve the issue.

Best Regards,
Charlie Choi

Was this reply helpful? Yes No
Jojo222813 64 on at

Like (0)

Report

Hi @v-yujincui-msft
I have tried to create a new flow and it works now.
Thanks.

Was this reply helpful? Yes No
adeHyp 2 on at

Like (0)

Report

The input body for trigger 'manual' of type 'Request' did not match its schema definition. Error details: 'Invalid type. Expected String but got Null., Invalid type. Expected String but got Null.'.
There's an issue with the manual triggers, it's not worked all day

Was this reply helpful? Yes No
sagirkazi 23 on at

Like (1)

Report

The "Accepted Solution" doesn't help solve the issue mentioned, Neither the suggestion to create a new flow everytime we run into this issue. Please unmark this post as Resolved since this is the first post users land to when searching for this error. Thanks.

Was this reply helpful? Yes No
sagirkazi 23 on at

Like (0)

Report
After banging my head around for 2 days, below is the workaround that I found that worked for me.
Do NOT test your workflow from the "Test" button inside the editor. The testing works but later when you actually run the flow, it gave me the error. Every time, Save you flow and go and actually trigger the event that supposed to trigger the flow.

Toggle the "Split On" button (turn off and ON again) on the Trigger action (first action in the flow) and click "Done" and save the flow. Execute the flow from actual trigger and not the TEST button on top-right corner.

Hope this helps!

Was this reply helpful? Yes No
Jojo222813 64 on at

Like (0)

Report

@sagirkazi , Thanks for the workaround. Let me try it. It is very strange to me that using "Test" will lead to this error.

Was this reply helpful? Yes No