cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
ericonline
Community Champion
Community Champion

HELP: Nested JSON Nightmare!

"Calling all cars!" Help! Days in, sooooo close. Need your eyes!

Schema in Collection: Works just fine.

{
    "LEVEL1": [
        {
            "LEVEL2": {
                "dontWorry": "aboutMe"
            },
            "LEVEL2": {
                "dontWorry": "aboutMe"
            },
            "LEVEL2": [
                {
                    "LEVEL3": [
                        {
                            "LEVEL4": "thing",
                            "LEVEL4_A": {
                                "ID": "1234",
                            },
                            "LEVEL4_B": {
                                "thingToPatch1": "Y",
"thingToPatch2": "X"
} } ] } ] } ] }

PROBLEM

  • I need to look at LEVEL4_A ID and Patch LEVEL4_B thingToPatch.
  • I cannot for the life of me figure out what to put in the { } !

SOOO CLOSE WITH THIS:

Patch(
    First(
        First(
            colCollection.LEVEL2
        ).LEVEL2.LEVEL3
    ).LEVEL3.LEVEL4_A,

LookUp(
        First(
            First(
                colCollection.LEVEL2
            ).LEVEL2.LEVEL3
        ).LEVEL4_A.ID,
    LEVEL4_A.ID = ThisItem.LEVEL4_A.ID
),

    {
        WHAT ON EARTH GOES HERE?
    }

)

I cannot find a value that works for the Patch({update}). 
Has anyone faced this before? I'm a few days in now and wondering if I hit a limit in PowerApps.
(Definitely hit a limit in my understanding). Any ideas #PowerHomies?

@RandyHayes , @timl , @wyotim , @RusselThomas , @Drrickryp , @mr-dang@KickingApps 

1 ACCEPTED SOLUTION

Accepted Solutions

Some more big ideas:

  • If you see [], this indicates a table. You'll need to use First() then .value to drill into the first one.
  • If you only see {} this is just an object/record. You can drill in directly using dot notation (level1.level2.level3)
  • I didn't study your schema. I was using First() and intellisense to figure it out. This is a good strategy for exploring new APIs.

 

If the API is only consumed in PowerApps and Flow, by all means keep its schema simple. It is a luxury to have control over your output.

 

If its schema is important for showing hierarchy of data and it's used elsewhere, then keep the complexity. In PowerApps and Flow, pancake it to the parts you need. Then do some concatenation to open it it up again when you need to POST.

 

To do 50 at a time, you'll wrap ForAll around Patch. There's a few threads on this forum on that pattern.

View solution in original post

23 REPLIES 23

@ericonline 

You're in too deep!! Smiley LOL

 

At a glance, I would say there is a flaw in your lookup...it would return the LEVEL4_A record...not the LEVEL4_B record that you are trying to patch.

Perhaps take a look at that factor.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!
Eloy
Advocate II
Advocate II

Maybe you already know this but what goes there is the record you want to update in the format {fieldname: 'Value to change to"}

 

Patch( datasource,filter record you want to find,{field:new value} )

So assuming you have the correct record filtered

Patch(
    First(
        First(
            colCollection.LEVEL2
        ).LEVEL2.LEVEL3
    ).LEVEL3.LEVEL4_A,

LookUp(
        First(
            First(
                colCollection.LEVEL2
            ).LEVEL2.LEVEL3
        ).LEVEL4_A.ID,
    LEVEL4_A.ID = ThisItem.LEVEL4_A.ID
),

    {
        thingToPatch:"new Value"
    }

)

If that is not the case, then you have to look at making sure you have found the correct record to update on the second Patch parameter, being the long code you have First( First( .....

 

Thanks for the reply @RandyHayes !

The way I'm thinking: 
Use the Lookup to reference 4_A as it is the ID of the record, then where matching, Patch 4_B value.

Thank you @Eloy for the thoughtful response. I think I found the correct syntax for the UPDATE. 

{
       LEVEL4_B:{
            thingToPatch: "value"
        }
}

Now perhaps the Lookup() is the culprit! Eyeyeye

wyotim
Resident Rockstar
Resident Rockstar

I came to say what @RandyHayes said.

And also, wow!

And furthermore, maybe you could put a temporary text box in and use your LookUp section in the code you posted to see what is going on by putting a period at the end and seeing what Intellisense suggests? When I am getting in the thick of it, little stuff like that helps me find what is going on. I am sure you have probably done something like that, but just in case you haven't. 

 

 

Thanks @wyotim . Unfortunately, this isn't a flat table.
My thought was that the LookUp is looking into Level4_A for the ID, then Patching the corresponding record in LEVEL4_B.

image.png
I literally have the lil buzzards in the SAME GALLERY. 
image.png

Which is combined with a goofy:

AddColumns(
    First(
        First(
            colCollection.LEVEL2
        ).LEVEL2.LEVEL3
    ).LEVEL3,
    "LEVEL4_B",
    If(
        LEVEL4_B = "Y",
    1,0
    )
)

The label for the ID is set to: ThisItem.LEVEL4_A.ID
The label for the "thingToPatch" is set to: ThisItem.LEVEL4_B.thingToPatch
lord

Trying this out now. Please let me know if you've already resolved this, @ericonline.


@ericonline wrote:

 

{
    "LEVEL1": [
        {
            "LEVEL2": {
                "dontWorry": "aboutMe"
            },
            "LEVEL2": {
                "dontWorry": "aboutMe"
            },
            "LEVEL2": [
                {
                    "LEVEL3": [
                        {
                            "LEVEL4": "thing",
                            "LEVEL4_A": {
                                "ID": "1234",
                            },
                            "LEVEL4_B": {
                                "thingToPatch1": "Y",
"thingToPatch2": "X"
} } ] } ] } ] }

 


If I understand correctly, you want to:

  • look up the record matching the ID in LEVEL4_A
  • revise the content in thingToPatch1

Note I removed an extra comma

 


@ericonline wrote:

 

Patch(
    First(
        First(
            colCollection.LEVEL2
        ).LEVEL2.LEVEL3
    ).LEVEL3.LEVEL4_A,

LookUp(
        First(
            First(
                colCollection.LEVEL2
            ).LEVEL2.LEVEL3
        ).LEVEL4_A.ID,
    LEVEL4_A.ID = ThisItem.LEVEL4_A.ID
),

    {
        WHAT ON EARTH GOES HERE?
    }

)

 


  • The first argument needs to be a table at the top level.
  • The second argument needs to be a record. The first argument of the LookUp needs to be a table with identical schema to the table that you're patching.
  • Between curly braces, you'll place the content you're updating. Normally, you patch content at the top level and would only show schema that you are updating. Since you're updating many levels deep, you'll need the schema and content for all fields above it.
    Note: there are many patterns that you can do in Patch; I'm describing the most common one.

 

I'll be attaching an app file with commenting code on what you'll need to do as an example. 

Attached is the app with a suggested Patch statement.

 

Please note, revising content many levels deep is not easy.

 

My suggestion is since this is a collection, make it shaped the way you want. Flatten the schema by adding columns at the top level that pull up content from deeper levels. Only keep the content you care about.

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

Users online (799)