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…
Continue Reading Nishant Rana’s Article on their blog
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.
Blog Syndicated with Nishant Rana’s Permission
More About This Author
Array
Dyn365CE23 April 2024Portal does not load and displays “Server Error” or shows “Getting set up.. This might take a while” message -Portal Startup Issue (PowerApps Portal)
Dyn365CE22 April 2024Versioning and Drafts for Solution-based Cloud Flows – Power Automate
Dyn365CE16 April 2024What will happen on changing the password of the user account used as the Owner of Cloud Flow and for Connection – Power Automate
Dyn365CE15 April 2024Using Focused view in Dynamics 365
