Fixed – Invalid type. Expected Integer but got Number (Power Automate)
In one of our Cloud Flows, for Parse JSON action, we got the below error – ValidationFailed. The schema validation Failed. “Invalid type. Expected Integer but got Number” The generated schema had data type defined as integer instead of number type for certain properties, and the response was having decimal value to it. So replacing … Continue reading "Fixed – Invalid type. Expected Integer but got Number (Power Automate)"
Published on:
Learn moreRelated posts
Use PowerFX in Power Automate Desktop Flow
21 hours ago
Power Automate – Upcoming changes to flow sharing experience
Starting in June 2025, we are updating the prerequisites for sharing cloud flows. With this update, users must be members of the environment w...
3 days ago
[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...
4 days ago
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...
12 days ago
Starts Tomorrow! Power Automate Training
15 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...
17 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...
17 days ago