Unlock the Full Potential of Parse JSON in Power Automate

[@jibbsautomations]

Paul, your videos on JSON in PA have been super helpful for me, thank you!

[@PaulieM]

I appreciate that. Thank you 🙏

[@Sloal]

That is the best intro to a KZbin video ever!!! Super useful tips. Thanks for sharing.

[@jamesclark2020]

This definitely opens up a lot of possibilities to explore.

[@JumpUpJumpUpandPowerPlatform]

This may well be the first Power Platform video I've watched the entire way through without skipping. Very very cool.

[@PaulieM]

Glad it was helpful. I felt like I’d unlocked a cheat code when I found that functionality 😂

[@FullRewardMinistries]

I wasn't one minute in before I figured out how to do something I'd been trying to do for 12 hours!!! Power Automate didn't give me any helpful tips, and I knew what I was doing was super simple. I had been trying to extract all of the values in one list and migrate it to another. I had some lists with friendly text that I could not preserve without separating the friendly text from the URL. Now that I have the first step down all I need to do is learn how to pull the friendly text and URL out and put them back together! Thank you!!!!!

[@PaulieM]

Brilliant to hear! Lot of hidden gems in that action!

[@nivednambiar6845]

Got to learn deeper about Parse JSON, was not aware these advance things can be done with this action. Great explanation paul :)😊

[@PaulieM]

It’s possible to go even further than I did in this video - but didn’t want to make it too long! Glad you enjoyed!

[@franknielsen3219]

You are a truly wizard with Power Auotmate 👌👌👌👌

[@365g]

Classic Paulie M... loads of valuable nuggets, loved the intro :)

[@nguyenmanhtuan1772]

Yes I did learn many new things about Parse JSON, thank you very much, Sir :)

[@PaulieM]

You are most welcome

[@chrisnicol8175]

Love the intro Paul! And thanks, I know this will be super useful.

[@fogila]

Thanks Paul, good stuff.

[@temidayolonge4566]

Hello Paul. Happy New Year. This is gold. Thanks as always

[@PaulieM]

Thank you! 🙏

[@trl_lrt]

Great video! These details and foundation are needed for anyone working with json data. It would be great to dive into the pros and cons of using parse json vs not using it. I've been testing flows that respond back to powerapps and I have the same api output sent back as raw variable outputs['HTTPS']?['body'] (not using parse json) and then the same but using the dynamic content generated from parse json step that is just the variable reference of 'body'. But then back in powerapps attempting to work with even basic data is complex. Understanding how to access nested child nodes depending on the different formats of json received back into powerapps would be really great to understand more detail.

[@avinoamrothenberg1244]

😊 Great explanation as always

[@antonioskokiantonis7051]

Great stuff!

[@PaulieM]

Yeah - some interesting nuggets in there. Glad you enjoyed

I liked that video before the warning message started ❤

[@karolzareba9003]

Man! Why i didn't saw this 1y ago!

[@PaulieM]

I guess because I only made it a week ago? But still I am glad you enjoyed it. Keep your eyes peeled for another video this week!

[@AdiCristea]

Paul: "we're going to embark on a 20 mins journey about JSON and it's going to be tedious" Me, at the end of the video: "wait, is that it? I need mooooooooooooore!!" This was exceptional, thank you, Paul!!!

[@PaulieM]

I could have gone on and on! 😂

[@AdiCristea]

@@PaulieM the resource is gold also, just going through it as we speak

[@AdiCristea]

@@PaulieM PS. good bye Select (in some cases), which actually applies to the other video from today too :)

[@PaulieM]

@@AdiCristea yes, lots of good stuff in there. Let me know what you find that is useful!

[@PaulieM]

@@AdiCristea check out enum, I really should have included that in the video!

[@geralddahl9159]

Thx for sharing this - not boring at all. First question: Why the need to tweek the output of the Send an HTTP Request to SharePoint around the 1:34 - 1:47 mark of video? Second question: I can't wrap my head around how at the 3:34 mark one has the ability to adjust the schema of the Parse JSON such that the output is passed on to the subsequent compose step as a highly delineated object with nuanced reference to firstName, email etc. My tiny chip brain gets stuck when it tries to imagine the Parse JSON step in Power Automate studying what it receives from the HTTP response step - it only sees field_1 field_2 etc. From what I see you doing, it appears one has the 'power' to input one's own preference within the Parse JSON step so as to suggest that, going forward, Power Automate append the structure/definition that the user wants as part of the way it outputs the payload going forward. I'm probably not clearly explaining the concept that my mind envisions is happening around all of this. It seems incongruent/dissonant - I would have imagined that a declaration like that would have caused an error. If you are able to understand what I'm chewing on and then confirm that I'm understanding things rightly, or rephrase how I should be understanding, your feedback would be welcome. Finally, two takeaways I did get: (1) never knew that a description could be added that would appear as part of the dynamic choice interface; (2) love your treatment on nulls, especially the one that allows the affected object to continue to show as a displayed dynamic option in the interface.

[@PaulieM]

First Question: I could have done it without tweaking the output but that would have made the parsing more complex. I was simply accessing the "Value" output of the HTTP action, because it could also return the nextlink property at the same level. Second Question: The JSON Schema provided to the Parse JSON action is still aware of the original field names (Field_1 etc) but we have decorated the schema with more details. Internally it will still be accessing the data via the original field names, but subsequent actions will output the more user friendly details we have provided in the schema. The treatment of the nulls is a great solution to a long standing problem. It was actually someone else that commented on another of my videos that provided that solution and the inspiration for this video.

[@geralddahl9159]

@@PaulieM thanks!

[@ukm365]

Someone has fallen asleep on the keyboard with the JSON schema site loaded up!! 😏

[@janvanhaver6970]

I've definitely watched 1 hour Power Automate videos that have brought me less value than these 20 minutes 😅 Super useful tips! One question, though: why did you not release this 6 months ago? 😉 (We have a D365 on prem to online migration running this weekend)

[@PaulieM]

I only recently discovered the hidden potential in the action (which has since led me to find other stuff). Apologies! Glad you for it useful!

[@ukm365]

I think that last one is the REAL hack, here. I didn't know that you could lean on the Parse JSON to validate in the middle of a flow. It stands to reason, and that email thing is SOOOOOOOOOOOOOOOOOOOOOOO required by so many things. I predict me using it in answers on the community about ... I dunno ... a bazillion times. XD

[@PaulieM]

yeah, that part is really cool. Quite a lot of things you can unearth there.

[@juliusm367]

Hi Paul, can you please help create an automated event triggered by an email. The start and end times of the event must be as stipulated in the body of the email. the subject of the event must be the subject of the email.

[@ukm365]

hahaha ... This is what I say before most things I talk about ... about anything!

[@yaynative]

I thought I knew something about JSON 🤦‍♂️

[@PaulieM]

Now you know a bit more 😀