Normally when we want to parse JSON content from an API in Power Automate, we use sample data and create the JSON schema to parse it using the option ‘Generate from sample’ :
This speeds up the process, however if we have a case where we have separate children properties with the same names, it’s hard to know what is the exact property when accessing it from the Dynamic Content pane, unless you add them and hover over the value to know the exact path until it.
In the example below we are creating an event using the Graph API:
Then we use the Parse JSON action to parse the outputs of the HTTP request to Graph, using the automatically generated schema:
When accessing the outputs from the Parse JSON action in a compose action later, the end and start dates values and time zones are shown with the same names:
However, with a simple tweak, we can relabel those properties and distinguish them easily.
For any property you…
More About This Author
SharePoint and Office 365 Consultant/Developer always trying to get the best from Microsoft stack (Microsoft 365/Azure/Power Platform and related stuff).
Living in Ireland since 2018, I had previously worked in Brazil as a consultant/developer for Office 365, SharePoint and related technologies for almost 10 years.
- ModernWorkplace2022.06.08Updating list views JSON formatters for a SharePoint list using Power Automate
- ModernWorkplace2022.05.19SharePoint lists custom View and Edit Buttons using JSON Formatting
- ModernWorkplace2022.05.14Power Apps: Patch data from the Office 365 Users connector to a SharePoint multi-user field without using collect
- ModernWorkplace2022.04.30Glossary View formatting: JSON Template including Related Link