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
Dyn365CE16 July 2024Set an app (Model-driven or Canvas App) as a startup app – Power Apps Mobile
Dyn365CE16 July 2024Mobile Offline Profile – Select columns to be downloaded (Dynamics 365 / Model-driven apps)
Dyn365CE10 July 2024Perform Age calculation using Formula Columns in Dataverse / Dynamics 365
Dyn365CE8 July 2024Using Homogenous Batch / Bulk operation messages for improved performance – Data Migration / Dataverse