cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
JorisdG
Power Apps
Power Apps

ParseJSON feedback

It’s been roughly two months since we released ParseJSON as an experimental feature in Power Apps. A lot of scenarios for makers have been unblocked with this feature, and we’ve seen great uptake even though it’s still considered experimental. We’re anxious to get this out of that experimental status. I wanted to take the opportunity to highlight a recent improvement, and address feedback with some of the future plans we have once we take ParseJSON (and untyped objects) out of the experimental phase.

Finally, and most importantly, I’m asking for your feedback. I will elaborate below but if you’re using ParseJSON I would love to hear from you. We’ve seen comparatively low feedback given the amount of usage. This is probably a good sign, but it makes us a little nervous pushing to preview or GA without making sure there aren’t any issues we just haven’t heard about.

 

Update since experimental launch

You can now use ForAll(), like Index(), directly on an untyped object. A JSON object array such as [ { “id”: 1, “Title”: “One” }, { “id”: 2, “Title”: “Two” } ] would previously require a Table(ParseJSON()) call before going to ForAll. This has the added drawback of resulting in a single-column table with untyped objects, so you would get something like:

 

ForAll( Table(untypedObject), { id: Value(ThisRecord.Value.id) )

 

requiring you to use the .Value field on ThisRecord for the single-column table. You can now pass untyped objects directly into ForAll, which no longer creates a single-column table requiring the use of the Value column. So the previous example becomes:

 

ForAll( untypedObject, { id: Value(ThisRecord.id) )

 

 

Feedback so far

The feedback we’ve received so far is positive in that this feature unblocks many scenarios involving JSON. There are two recurring points of feedback we’ve heard from multiple customers:

 

  1. The feature is very “verbose” today due to the requirement of casting every field individually to a specific type. If you set a table of untyped objects as the Items source of a gallery, each use of a field requires Value(), Text() and other casting everywhere you wish to use the fields. For now you can consider using ForAll to type everything into a typed table first, as shown above, making field access easier. Our ultimate goal is to allow you to define your own type schemas and cast the whole JSON to it. We envision this feature to be used with the ParseJSON() function, where you pass in the JSON string as well as the type you defined, and the result of ParseJSON() would then be a typed object as opposed to an untyped object that requires casting. To be clear, we intend to GA ParseJSON with untyped objects first, and add the new typing features later on.

 

  1. Using ParseJSON() with connectors. If a column from a datasource contains a string with JSON, that is easy enough. But we’ve heard of scenarios where makers want to take the whole response message from a connector and manually parse the JSON when the app runs. The connector team is looking to build on top of our work with untyped objects, and beyond that also the previously mentioned type schema definitions to take connectors to a new level. The experimental Dynamic Schema feature is great but is missing some features and flexibility in Power Fx, and we’re starting to address those in Power Fx (with untyped objects and type definitions). There’s some short and long term work going on that I hope you will get to hear about soon.

 

If you have any feedback or concrete scenarios you’d like to share, I'd love it if you could comment on this thread. I would love to understand how you’re using ParseJSON or trying to use ParseJSON!

49 REPLIES 49
adrianoc
New Member

We have fed back internally through the partners we're working with on Microsoft Fast Track, but I wanted to reiterate here that this ParseJson function, even in its experimental form, is a huge improvement over existing patterns for consuming data from external APIs for display/processing in the app.

 

We have an app that is designed to allow users to search a third party API, and then that data can be used to fill out details on other records. Previously we used a Flow to call the API and the flow created records in a custom Dataverse table, and then we displayed the results in the app directly from table with a filter. That was extremely slow, mostly because it just took a long time to process the steps in the Flow. Returning the API response directly and displaying it with Table(ParseJson()) gave a massive boost to performance.

 

I will say that the syntax feels a little obscure/strained to me, especially with lots of nested JSON from a Graphql query (for example) needing chained Index()es , but I am not a Canvas App expert -- this is the first time I've ever seen Canvas Apps -- so this feeling might be my lack of understanding of the design goals for this tool. I notice you've updated this post to say that the type casting requirements have been improved, but I actually didn't mind the explicit casts, I felt they made it a little clearer to scan what was going on in the data.

 

I would love to see this function move out of experimental and into preview, we'd very much like to use this feature more widely.

rodneyb
Frequent Visitor

This feature opened up a whole range of capabilities for me as I use a single PCF to request commands and return json.

 

One blocker that has come up just now is what seems to be this: If the ParseJson call used to populate a collection, it does not appear to be completed when, say, a Navigate is called immediately after. I get the collection but only one row with the value "true" populated in a new column called "Value". If I eliminate the navigation, it builds the collection fine (I've been using ParseJSON quite extensively for the last month).

 

Is the ParseJson in fact an asynchronous operation? Thanks, Rodney

 

P.S. This issue only shows up after publishing and viewing on an android tablet or phone. Editing or playing on the desktop does not exhibit the issue (not sure about apple).

Are you using Collect() or ClearCollect() to populate the collection? And on mobile you're using the main Power Apps app I assume?

rodneyb
Frequent Visitor

Yes, ClearCollect. I'm not sure what you mean when you mention "main Power Apps app". Do you mean as opposed to a direct url?

 

As an aside, I have noticed that most connectors or actions seem to be asynchronous. Unless, for example, I check for, say, the result of a Flow. Then the code waits and I'm able to check result success. In fact, to counter that behavior when I want speed but need stuff to wait on other stuff, I created a queue system so Flow calls (and results checked) happen in a separate thread.

 

Here's the code just before I call Navigate. The next screen's data call only works (99% of the time) because, on the next screen I implement a 200ms delay with a Timer. It's notable, too I think, that, without the Timer or any other hack, the data on the next screen will load correctly every time after the first navigation back/forth. As if it needed a one-time cache to load:

 

      ClearCollect(collAllProductsZASSLocations, 
        ForAll( ParseJSON( actionslocationsdata ) , 
        { 
            sProductName: Text(ThisRecord.Value.sProduct), 
            sCount: Value(ThisRecord.Value.sCount),
            iProductID: Value(ThisRecord.Value.iProductID) 
        });
        //UpdateContext({startDelay:true})
         //Notify("naving", Success, 4000);
         Navigate(screenAllZASSLocations)

 

Let me know if that doesn't make sense.

 

 

 

Thanks, Rodney

PavelSheludkov
Advocate I
Advocate I

Just gave this feature a go while evaluating an SQL On-Prem integration scenario.

It works well and allow to easily parse flow response that running a stored procedure to obtain required data.

Any updates on when ParseJSON feature is going to move to Preview?

LaelLeeH
Helper II
Helper II

Hi @JorisdG 

I have until now been using Match and MatchAll to manually parse json strings. I recently started swapping over to ParseJSON and so far so good, but I am now battling with a nested JSON array of records.

My Match statement was:

LaelLeeH_0-1674101747987.png

 ... where the last field ProcessPerformersJSON, is a nested JSON array of records which I Parse at a later date into another collection

My new ParseJSON looks as follows:

LaelLeeH_1-1674101826956.png

But that last conversion is throwing an error:

LaelLeeH_2-1674107531301.png

I have tried replacing Text(ThisRecord.Value.ProcessPerformersJSON) with  Table(ThisRecord.Value.ProcessPerformersJSON) and with Text(ThisRecord.ProcessPerformersJSON) and with an entire ForAll to Parse the nested table and I can't get anything to work. 

 

I can send you a copy of my incoming JSON string privately if necessary.

Any assistance you can provide will be greatly appreciated.

Thanks

Regards

Lael

 

LaelLeeH
Helper II
Helper II

Hi @JorisdG 

I have another scenario where I have been using string manipulation up until now, and it works perfectly but it is ugly and I am sure it is not too performant either.  I would love to replace it with ParseJSON if possible.  However, the JSON field name is dynamic (or passed in to the string manipulation as a parameter) and I am not sure if this is possible with ParseJSON.

 

My current manipulation looks something like this. See InputValue: in the code below:

ClearCollect(

            colFormFields,

            AddColumns(

                        colMyHeaderAttributes,

                "InputValue",

                                                    Mid(

                                                        First(

                                                            Split(

                                                                Mid(

                                                                    _lSelectedTransaction.jsonCol,

                                                                    Coalesce(

                                                                        Find(

                                                                            """" & jsonName & """:",

                                                                            _lSelectedTransaction.jsonCol

                                                                        ),

                                                                        99999999

                                                                    ),

                                                                    Len(_lSelectedTransaction.jsonCol)

                                                                ),

                                                                ","""

                                                            )

                                                        ).Result,

                                                        Find(

                                                            ":",

                                                            First(

                                                                Split(

                                                                    Mid(

                                                                        _lSelectedTransaction.jsonCol,

                                                                        Coalesce(

                                                                            Find(

                                                                                """" & jsonName & """:",

                                                                                _lSelectedTransaction.jsonCol

                                                                            ),

                                                                            99999999

                                                                        ),

                                                                        Len(_lSelectedTransaction.jsonCol)

                                                                    ),

                                                                    ","""

                                                                )

                                                            ).Result

                                                        ) + 1,

                                                        (Len(

                                                            First(

                                                                Split(

                                                                    Mid(

                                                                        _lSelectedTransaction.jsonCol,

                                                                        Coalesce(

                                                                            Find(

                                                                                """" & jsonName & """:",

                                                                                _lSelectedTransaction.jsonCol

                                                                            ),

                                                                            99999999

                                                                        ),

                                                                        Len(_lSelectedTransaction.jsonCol)

                                                                    ),

                                                                    ","""

                                                                )

                                                            ).Result

                                                        ))

                                                    )

jsonName  refers to a field in colMyHeaderAttributes, and so is dynamic per record being added to the collection

Also, _lSelectedTransaction.jsonCol is not a unique json structure.  I have multiple different 'Transaction' types all configured with different jsonCol field naming structures, and hence the need to look up the jsonName in colMyHeaderAttributes

 

I have been trying to replace the above with something like this:

InputValue : Text(ParseJSON(_lSelectedTransaction.jsonCol).@jsonName)

or 

InputValue : Text(ParseJSON(_lSelectedTransaction.jsonCol).colMyHeaderAttributes[@jsonName])

Obviously both fail, and I totally understand why.  Is what I am trying to do possible by some other means?  It will make a massive difference to my app if I can get it to work. 

Thanks, in the sincere hopes of a successful outcome 😉

Regards

Lael

LaelLeeH
Helper II
Helper II

Hi @JorisdG 

 

Are you able to have a look at my two issues below and respond.  Getting them working will allow me to make some significant performance improvements to my app which are very sorely needed.  Will really appreciate a response.

 

Many thanks

Regards

Lael

JorisdG
Power Apps
Power Apps

Sorry for the late reply. Unfortunately we don't have a way to access a property by its name dynamically. It's something we've discussed in the past but we have no designs or anything on the roadmap at the moment.

Helpful resources

Announcements

Exclusive LIVE Community Event: Power Apps Copilot Coffee Chat with Copilot Studio Product Team

  It's time for the SECOND Power Apps Copilot Coffee Chat featuring the Copilot Studio product team, which will be held LIVE on April 3, 2024 at 9:30 AM Pacific Daylight Time (PDT).     This is an incredible opportunity to connect with members of the Copilot Studio product team and ask them anything about Copilot Studio. We'll share our special guests with you shortly--but we want to encourage to mark your calendars now because you will not want to miss the conversation.   This live event will give you the unique opportunity to learn more about Copilot Studio plans, where we’ll focus, and get insight into upcoming features. We’re looking forward to hearing from the community, so bring your questions!   TO GET ACCESS TO THIS EXCLUSIVE AMA: Kudo this post to reserve your spot! Reserve your spot now by kudoing this post.  Reservations will be prioritized on when your kudo for the post comes through, so don't wait! Click that "kudo button" today.   Invitations will be sent on April 2nd.Users posting Kudos after April 2nd. at 9AM PDT may not receive an invitation but will be able to view the session online after conclusion of the event. Give your "kudo" today and mark your calendars for April 3rd, 2024 at 9:30 AM PDT and join us for an engaging and informative session!

Tuesday Tip: Unlocking Community Achievements and Earning Badges

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!     THIS WEEK'S TIP: Unlocking Achievements and Earning BadgesAcross the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. These badges each signify a different achievement--and all of those achievements are available to any Community member! If you're a seasoned pro or just getting started, you too can earn badges for the great work you do. Check out some details on Community badges below--and find out more in the detailed link at the end of the article!       A Diverse Range of Badges to Collect The badges you can earn in the Community cover a wide array of activities, including: Kudos Received: Acknowledges the number of times a user’s post has been appreciated with a “Kudo.”Kudos Given: Highlights the user’s generosity in recognizing others’ contributions.Topics Created: Tracks the number of discussions initiated by a user.Solutions Provided: Celebrates the instances where a user’s response is marked as the correct solution.Reply: Counts the number of times a user has engaged with community discussions.Blog Contributor: Honors those who contribute valuable content and are invited to write for the community blog.       A Community Evolving Together Badges are not only a great way to recognize outstanding contributions of our amazing Community members--they are also a way to continue fostering a collaborative and supportive environment. As you continue to share your knowledge and assist each other these badges serve as a visual representation of your valuable contributions.   Find out more about badges in these Community Support pages in each Community: All About Community Badges - Power Apps CommunityAll About Community Badges - Power Automate CommunityAll About Community Badges - Copilot Studio CommunityAll About Community Badges - Power Pages Community

Tuesday Tips: Powering Up Your Community Profile

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!   This Week's Tip: Power Up Your Profile!  🚀 It's where every Community member gets their start, and it's essential that you keep it updated! Your Community User Profile is how you're able to get messages, post solutions, ask questions--and as you rank up, it's where your badges will appear and how you'll be known when you start blogging in the Community Blog. Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile.     Password Puzzles? No Problem! Find out how to sync your Azure AD password with your community account, ensuring a seamless sign-in. No separate passwords to remember! Job Jumps & Email Swaps Changed jobs? Got a new email? Fear not! You'll find out how to link your shiny new email to your existing community account, keeping your contributions and connections intact. Username Uncertainties Unraveled Picking the perfect username is crucial--and sometimes the original choice you signed up with doesn't fit as well as you may have thought. There's a quick way to request an update here--but remember, your username is your community identity, so choose wisely. "Need Admin Approval" Warning Window? If you see this error message while using the community, don't worry. A simple process will help you get where you need to go. If you still need assistance, find out how to contact your Community Support team. Whatever you're looking for, when it comes to your profile, the Community Account Support Knowledge Base article is your treasure trove of tips as you navigate the nuances of your Community Profile. It’s the ultimate resource for keeping your digital identity in tip-top shape while engaging with the Power Platform Community. So, dive in and power up your profile today!  💪🚀   Community Account Support | Power Apps Community Account Support | Power AutomateCommunity Account Support | Copilot Studio  Community Account Support | Power Pages

Super User of the Month | Chris Piasecki

In our 2nd installment of this new ongoing feature in the Community, we're thrilled to announce that Chris Piasecki is our Super User of the Month for March 2024. If you've been in the Community for a while, we're sure you've seen a comment or marked one of Chris' helpful tips as a solution--he's been a Super User for SEVEN consecutive seasons!       Since authoring his first reply in April 2020 to his most recent achievement organizing the Canadian Power Platform Summit this month, Chris has helped countless Community members with his insights and expertise. In addition to being a Super User, Chris is also a User Group leader, Microsoft MVP, and a featured speaker at the Microsoft Power Platform Conference. His contributions to the new SUIT program, along with his joyous personality and willingness to jump in and help so many members has made Chris a fixture in the Power Platform Community.   When Chris isn't authoring solutions or organizing events, he's actively leading Piasecki Consulting, specializing in solution architecture, integration, DevOps, and more--helping clients discover how to strategize and implement Microsoft's technology platforms. We are grateful for Chris' insightful help in the Community and look forward to even more amazing milestones as he continues to assist so many with his great tips, solutions--always with a smile and a great sense of humor.You can find Chris in the Community and on LinkedIn. Thanks for being such a SUPER user, Chris! 💪🌠

Tuesday Tips: Community Ranks and YOU

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!This Week: Community Ranks--Moving from "Member" to "Community Champion"   Have you ever wondered how your fellow community members ascend the ranks within our community? What sets apart an Advocate from a Helper, or a Solution Sage from a Community Champion? In today’s #TuesdayTip, we’re unveiling the secrets and sharing tips to help YOU elevate your ranking—and why it matters to our vibrant communities. Community ranks serve as a window into a member’s role and activity. They celebrate your accomplishments and reveal whether someone has been actively contributing and assisting others. For instance, a Super User is someone who has been exceptionally helpful and engaged. Some ranks even come with special permissions, especially those related to community management. As you actively participate—whether by creating new topics, providing solutions, or earning kudos—your rank can climb. Each time you achieve a new rank, you’ll receive an email notification. Look out for the icon and rank name displayed next to your username—it’s a badge of honor! Fun fact: Your Community Engagement Team keeps an eye on these ranks, recognizing the most passionate and active community members. So shine brightly with valuable content, and you might just earn well-deserved recognition! Where can you see someone’s rank? When viewing a post, you’ll find a member’s rank to the left of their name.Click on a username to explore their profile, where their rank is prominently displayed. What about the ranks themselves? New members start as New Members, progressing to Regular Visitors, and then Frequent Visitors.Beyond that, we have a categorized system: Kudo Ranks: Earned through kudos (teal icons).Post Ranks: Based on your posts (purple icons).Solution Ranks: Reflecting your solutions (green icons).Combo Ranks: These orange icons combine kudos, solutions, and posts. The top ranks have unique names, making your journey even more exciting! So dive in, collect those kudos, share solutions, and let’s see how high you can rank! 🌟 🚀   Check out the Using the Community boards in each of the communities for more helpful information!  Power Apps, Power Automate, Copilot Studio & Power Pages

Find Out What Makes Super Users So Super

We know many of you visit the Power Platform Communities to ask questions and receive answers. But do you know that many of our best answers and solutions come from Community members who are super active, helping anyone who needs a little help getting unstuck with Business Applications products? We call these dedicated Community members Super Users because they are the real heroes in the Community, willing to jump in whenever they can to help! Maybe you've encountered them yourself and they've solved some of your biggest questions. Have you ever wondered, "Why?"We interviewed several of our Super Users to understand what drives them to help in the Community--and discover the difference it has made in their lives as well! Take a look in our gallery today: What Motivates a Super User? - Power Platform Community (microsoft.com)

Top Kudoed Authors
Users online (4,525)