Loading...

[Resolved] Error: The input body for trigger ‘manual’ of type ‘Request’ did not match its schema definition. Error details: ‘Invalid type. Expected String but got Null.’. in POwer Automate Dataverse When a row selected trigger

[Resolved] Error: The input body for trigger ‘manual’ of type ‘Request’ did not match its schema definition. Error details: ‘Invalid type. Expected String but got Null.’. in POwer Automate Dataverse When a row selected trigger
If you are working with Power Automate and using “When a Row is Selected” Trigger then you may get the below error. This error has a work around you can follow. Solution: Do not use any dynamic content from Trigger step in any other action steps. Rather after the trigger, use one more step “Get…
Read more

Published on:

Learn more
Softchief Learn
Softchief Learn

The Power of Microsoft Dynamics 365 Consulting, Implementation & Online Training

Share post:

Related posts

Power Automate: Perform An AI Prompt On A PDF Document

Power Automate can be used to run an AI Prompt on a PDF document. It’s ... The post Power Automate: Perform An AI Prompt On A PDF Docume...

9 days ago

Power Automate – New IP Address Ranges for Power Automate flows using HTTP Actions

Beginning May 1, 2025, Power Automate flows will be leveraging additional service pools to execute flows. This change will impact flows with H...

13 days ago

Announcing the Process map public preview in Power Automate

We’re thrilled to announce the public preview of Process Map in Power Automate, a significant advancement for process-centric observability at...

14 days ago

Power Automate – Repair flow automation errors

We are announcing the Repair flow automation errors feature for Power Automate. This feature uses Copilot to find and repair automation errors...

15 days ago
Stay up to date with latest Microsoft Dynamics 365 and Power Platform news!
* Yes, I agree to the privacy policy