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

Yeah I responded to a similar question just a few posts ago in this thread. Repeating here:

 

we're finishing off a few new features for ParseJSON to make it less verbose and easier (shorter) to write formulas. This should be rolling out hopefully in a few more weeks. We'll likely move to supported preview and ultimately GA in the weeks/months after that. So I expect in mid to late March this will start moving quickly.

Hi @JorisdG 

 

Thanks for looking at this.

I tried it, and cannot get it to work my side. But, something I noticed looking at your code, is that it seems your version of Parsejson is returning Typed objects, and that the syntax is way less verbose. I see that you are not required to do the explicit conversion of the fields from untyped to typed data. 

 

I tried your notation with my nested json, and it failed. So I then tried just a simple ParseJSON without typing and it also failed. So, I guess the question is, is it possible that I somehow have an older/different version of ParseJSON to the version you are using above?

Regards

Lael  

 

Regards

Lael

Thank you for the feedback!!

The only formula showing in my screenshot is the ForAll, which doesn't require any type conversions. If you're talking about the screenshot of the gallery, each control you see there is explicitly typing the field... like Text(ThisItem.Field1) etc...

I'm getting the following error message if I'm trying to send an email with the ParseJSON/Untyped feature setting turned on:

 

"Office365Outlook.sendEmailV2 failed: The data returned in the response is invalid. Response data should be a valid JSON object."

 

I'm trying to send the email with just a simple code:

Office365Outlook.SendEmailV2(
    varUserSettings.UserEmail,
    "title text",
    "body text"
)

The email is sent regardless of the error message.

biterbit
Kudo Commander
Kudo Commander

I also have this issue (described in more detail in this post: Office365Outlook errors when ParseJSON and untyped). These runtime errors are also generated by calls to Power Automate flows and the same issue invalidates some uses of IfError() as described in this thread: Solved: Re: IfError error: Untyped objects cannot be used.

Anonymous
Not applicable

Also started experiencing this issue with the send an email v2 function in the last 48 hours or so (working fine prior to this). Hoping this can be resolved asap.

biterbit
Kudo Commander
Kudo Commander

@JorisdG Just wanted to ensure that you were aware of this issue with the ParseJSON and untyped objects feature and conflicts with the Office365Outlook connector and calls to Power Automate flows.

Thought i was going crazy and it was my flows breaking, but i'm also having this issue with my flows being called. The flow still works, just gives this error each time

@Zanzaid1 If you look towards the end of this thread, IfError error: Untyped objects cannot be used, you will find the workaround I used for my flows.

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Solution Authors
Users online (2,827)