cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
TheDonSimon
Frequent Visitor

Functions after Forall Patch not working

I have a forall patch function in my app, I know its slow and not the best performance however, the fields i am updating require a lookup from a different database so this fits my purpose the best. the problem is, any functions after the forall result in the patch returning blank values. The below formula works fine however, as mentioned any functions added after it leads to the patch resulting in blank results. 

I have tried the forall patch by itself and not with concurrent and the same thing happens, any function after it seems to result in blank returns.

Concurrent(
        ForAll(
        StoreItems,Patch(
            'IM PowerApp Testing Data',ThisRecord,
            {
                Price: Value(
                    LookUp(
                        'catalogue_data',
                        itemcode = 'Item ID'
                    ).purchaseprice
                ),
                UOM: LookUp(
                    'catalogue_data',
                    itemcode = 'Item ID'
                ).uomdescription,
                QOM: Value(
                    LookUp(
                        'catalogue_data',
                        itemcode = 'Item ID'
                    ).qom
                ),
                Description: LookUp(
                    'catalogue_data',
                    itemcode = 'Item ID'
                ).description
            }
        )
    ),
    Patch(
        'IVM Transaction Log',
        Defaults('IVM Transaction Log'),
        {
            Title: "StoreNxsUpdate",
            User: User().FullName,
            TimeStamp: Now(),
            Reqpoint: First(ReqpointInfo).SelectedReqpoint,
            StoreID: varStore
        }
    )
)

If anyone has any help that would be much appreciated and any tips for performance as well or alternative methods. 

1 ACCEPTED SOLUTION

Accepted Solutions

 

I've solved the issue, though I'm not sure if it’s a bug or something related to the `patch` function. After isolating the code, I found that the problem was with how `lookup` was used within the `patch` function. It seems PowerApps didn't like using `lookup` with the format `).desired`. When I changed it to `,desired)`, it worked perfectly.

For some reason, when using `patch` and `lookup` with the `).desired` format, followed by another function after `patch`, the `lookup` result ended up being blank, even though `lookup` was correctly obtaining a value. This behavior is quite strange.

 

View solution in original post

3 REPLIES 3
rzuber
Responsive Resident
Responsive Resident

Are you trying to patch to the IVM Transaction Log for each record in the ForAll() data source?

 

I'm a little confused about what the issue is. Can you clarify? Maybe provide some screenshots?

 

Her's a method to clean up that ForAll a bit..

 

ForAll(
    StoreItems,
    Patch(
        'IM PowerApp Testing Data',
        ThisRecord,
        With(
            {
                _catData: LookUp(
                    'catalogue_data',
                    itemcode = 'Item ID'
                )
            },
            {
                Price: Value(_catData.purchaseprice),
                UOM: _catData.uomdescription,
                QOM: Value(_catData.qom),
                Description: _catData.description
            }
        )
    )
)

 

If you're trying to patch both during the ForAll(), you want the Concurrent() inside the ForAll().. again, not sure here from your description.

 

ForAll(
    StoreItems,
    Concurrent(
        Patch(
            'IM PowerApp Testing Data',
            ThisRecord,
            With(
                {
                    _catData: LookUp(
                        'catalogue_data',
                        itemcode = 'Item ID'
                    )
                },
                {
                    Price: Value(_catData.purchaseprice),
                    UOM: _catData.uomdescription,
                    QOM: Value(_catData.qom),
                    Description: _catData.description
                }
            )
        ),
        Patch(
            'IVM Transaction Log',
            Defaults('IVM Transaction Log'),
            {
                Title: "StoreNxsUpdate",
                User: User().FullName,
                TimeStamp: Now(),
                Reqpoint: First(ReqpointInfo).SelectedReqpoint,
                StoreID: varStore
            }
        )
    )
)

 

 

After looking at this example, I can't see any reason why you would want to do it this way (unless ReqpointInfo is a column in StoreItems?).. but I am still confused. 😉

 

---

Or is this a situation where you need the second patch to happen after the ForAll?

If so, you probably want it like:

ForAll(
    StoreItems,
    Patch(
        'IM PowerApp Testing Data',
        ThisRecord,
        With(
            {
                _catData: LookUp(
                    'catalogue_data',
                    itemcode = 'Item ID'
                )
            },
            {
                Price: Value(_catData.purchaseprice),
                UOM: _catData.uomdescription,
                QOM: Value(_catData.qom),
                Description: _catData.description
            }
        )
    )
);
Patch(
    'IVM Transaction Log',
    Defaults('IVM Transaction Log'),
    {
        Title: "StoreNxsUpdate",
        User: User().FullName,
        TimeStamp: Now(),
        Reqpoint: First(ReqpointInfo).SelectedReqpoint,
        StoreID: varStore
    }
)

I apologise for not explaining this well initially. Here's some context:

In the database 'IM PowerApp Testing Data', which contains a list of products, I need to update certain fields like price and description using data from `catalogue_data`. Additionally, I need to track user actions, which is why I'm using a patch to the transaction log.

I initially thought using the `Concurrent` function would be faster since both patches (to the product data and the transaction log) don't need to be executed sequentially; they can run simultaneously.

However, I'm encountering a problem. When I place any function after the `ForAll` patch, the information patched to 'IM PowerApp Testing Data' returns blank. In contrast, if there is nothing after the `ForAll` patch, it works correctly.

My goal is to add a loading screen using the `UpdateContext` function to show and hide a loading spinner once the patch is completed. The final version should look like this:

UpdateContext({Loading:true});
Concurrent(
        ForAll(
        StoreItems,Patch(
            'IM PowerApp Testing Data',ThisRecord,
            {
                Price: Value(
                    LookUp(
                        'staging.nxs_catalogue_preprocessing',
                        itemcode = 'Item ID'
                    ).purchaseprice
                ),
                UOM: LookUp(
                    'staging.nxs_catalogue_preprocessing',
                    itemcode = 'Item ID'
                ).uomdescription,
                QOM: Value(
                    LookUp(
                        'staging.nxs_catalogue_preprocessing',
                        itemcode = 'Item ID'
                    ).qom
                ),
                Description: LookUp(
                    'staging.nxs_catalogue_preprocessing',
                    itemcode = 'Item ID'
                ).description
            }
        )
    ),
    Patch(
        'IVM Transaction Log',
        Defaults('IVM Transaction Log'),
        {
            Title: "StoreNxsUpdate",
            User: User().FullName,
            TimeStamp: Now(),
            Reqpoint: First(ReqpointInfo).SelectedReqpoint,
            StoreID: varStore
        }
    )
);UpdateContext({Loading:false})

But whenever I add anything after the `ForAll` patch, the data returned is blank, as shown:
Using the desired code this is the output

Before:

TheDonSimon_0-1718890501520.png

After:

TheDonSimon_1-1718890515592.png

Whereas if there is nothing after it, the data updates correctly if there was a price change:

Concurrent(
        ForAll(
        StoreItems,Patch(
            'IM PowerApp Testing Data',ThisRecord,
            {
                Price: Value(
                    LookUp(
                        'staging.nxs_catalogue_preprocessing',
                        itemcode = 'Item ID'
                    ).purchaseprice
                ),
                UOM: LookUp(
                    'staging.nxs_catalogue_preprocessing',
                    itemcode = 'Item ID'
                ).uomdescription,
                QOM: Value(
                    LookUp(
                        'staging.nxs_catalogue_preprocessing',
                        itemcode = 'Item ID'
                    ).qom
                ),
                Description: LookUp(
                    'staging.nxs_catalogue_preprocessing',
                    itemcode = 'Item ID'
                ).description
            }
        )
    ),
    Patch(
        'IVM Transaction Log',
        Defaults('IVM Transaction Log'),
        {
            Title: "StoreNxsUpdate",
            User: User().FullName,
            TimeStamp: Now(),
            Reqpoint: First(ReqpointInfo).SelectedReqpoint,
            StoreID: varStore
        }
    )
)

 

 

I've solved the issue, though I'm not sure if it’s a bug or something related to the `patch` function. After isolating the code, I found that the problem was with how `lookup` was used within the `patch` function. It seems PowerApps didn't like using `lookup` with the format `).desired`. When I changed it to `,desired)`, it worked perfectly.

For some reason, when using `patch` and `lookup` with the `).desired` format, followed by another function after `patch`, the `lookup` result ended up being blank, even though `lookup` was correctly obtaining a value. This behavior is quite strange.

 

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 (1,487)