Showing results for 
Search instead for 
Did you mean: 

Parse JSON in PowerApps

Hi everyone,


The new JSON function in PowerApps is great and we have been using it extensively. Another great addition would be to parse JSON directly in PowerApps. If PowerApps receives a stringified JSON string, it should be able to easily Parse this and use this data in the app, to write it into a collection, variable or whatever.


We have been using the HTTP response in flow to return dynamic data to PowerApps, but seeing that this is now longer included in the Office 365 entitlement and that normal Respond To PowerApps Flow action not supporting Arrays or JSON, this request is quite urgent.


Please let us know if you have any questions or suggestions.


Kind regards


Dawid van Heerden
Follow on Twitter: @davestechtips
Subscribe to YouTube:

Status: Under Review
Advocate III

Please make this happen.  This would be huge.

Advocate I

This is not the first time that I needed this and I wholeheartedly agree with everyone. This would be huge and improve the Flow - PowerApps interaction dramatically. Without this it is currently hardly possible to transfer objects or arrays from Flow to PowerApp. Yet, Flow is the only option to send http requests to sharepoint and get tricky information such as 'ListItemEntityTypeFullName'. I would love this option, in fact, so much, that I already came up with a more or less hacky workaround. A proper way to achieve this would still be preferrable though 🙂 

Frequent Visitor

Yes Please


Advocate II

Think its clear for everyone - this would be a huge plus.

Advocate I

Absolutely a great feature to have!

Advocate V

Yes, PLEASE!  And to echo  @ZePowerDiver , the ability to quickly parse JSON into a collection would be SWEET.  Anybody dealing with Flow + Power Apps is eventually going to need to be able to move from JSON to a collection or the reverse.

Not applicable

Agreed! It is much needed. 

Frequent Visitor

Need this feature. Anyone got a workaround on this?

Advocate I

This would be huge.

Advocate I


I got a workaround for this. It is a bit hacky though, and of course you will need to rely on your systems' adherence to the rules, but basically you just create your own schema with your own delimiters. In my case I went for something along the lines of:


<DisplayName>John Doe<Email><FirstName>John<LastName>Doe<department>HR<EndOfEntry><DisplayName>Jane Doe<Email><FirstName>Jane<LastName>Doe<department>Sales<EndOfEntry>


In your PowerApp you'll need to first split for every "<EndOfEntry>" and then find every value for every field. This is a LOT to write in code and unfortunately I have opted for a different approach and thus lost my code segments in the meantime. But I know that it works. So if push comes to shove and you really need it, this is proven to work.