The JSON output in the run history of the List records action step from the Common Data Service (current environment) connector is useful for troubleshooting purposes or getting the sample data for Parse JSON action. It is also useful when you need to see the attributes which are not listed in ‘Dynamics content’ pane (e.g. OData.Community.Display.V1.FormattedValue properties, or attributes…
Continue Reading noreply@blogger.com (Linn Zaw Win)’s Article on their blog
Get JSON Output of Steps with Status Reason 200 in Power Automate
There are times when the output of List records action step from CDS (current environment) is shown as Status Reason: 200 instead of the Click to download URL which lets you open the JSON output, so how do you go about this?
Blog Syndicated with noreply@blogger.com (Linn Zaw Win)’s Permission
More About This Author
Array
- Dyn365CE4 March 2024Open New Record Form with Pre-populated Fields Using Xrm.Navigation.navigateTo
- Dyn365CE23 February 2024How to Fix Button in Modern Command Bar Disappearing After Grid Item Selection
- Dyn365CE16 February 2024Keep Your Dataverse Solution Clean and Simple
- Dyn365CE7 February 2024Refresh Main Form When New Child Row is Added in Subgrid via Quick Create Form in Model-Driven App