cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Ashok2
Post Partisan
Post Partisan

Powerapp slow performance

I am writing below formula on icon of gallery , if multiple checkbox are checked it will update multiple item status as per last status , but if I click it , will take long  time to update item and get item invisible from gallery 

ForAll(
    RenameColumns(Filter(Scope_1.AllItems,Checkbox3_1.Value),"ID","ID1"),
    Patch(
        Scopes,
        LookUp(Scopes,ID=ID1),{ awrWFInProgress:true,
        Status:{Value:
            Switch(
                LookUp(Scopes,ID=ID1).Status.Value,
           "Submitted", "Supported by Manager",
                "Supported by  Manager", "Supported by L2",
                "Pending with L2","Supported by L2",
                 "Supported by L2","Supported by L3","Not Supported by L2","Supported by L3","Reviewed by L4","Supported by L3"
            )
        }
       
        }
    )
)

 

 

 

And same for below formulae where I am updating forms this also take around 16 seconds to update an navigate back to gallery 

 

Refresh(Scopes); If(
    !Form1Section.Valid,
// Then
    SubmitForm(Form1Section),     !Form1Section_2.Valid,
// Then
    SubmitForm(Form1Section_2),
// Else
    Patch(
        Scopes, SelectedItem, AddSingleForm_1.Updates, Form1Section.Updates, Form1Section_2.Updates
    );
   Navigate(MyItemsView)
);

 

Any help on this to make performance much better

 

1 ACCEPTED SOLUTION

Accepted Solutions
WarrenBelz
Most Valuable Professional
Most Valuable Professional

No problem @Ashok2 ,

That was what I was trying to do - show you the principle of minimizing server calls and Collections and Variables are always the best way of doing this. As we both have discovered, trying to write code of this complexity without being able to see the data structure to test it is always challenging, particularly when one does things in a different manner.

On that subject, I will leave you with one thought - if you can make a Collection, even if it is done in a couple of stages that will directly Patch the data source "record for record", it will run very quickly and is actually the way I approach all filtering/renaming/field choosing for everything from Galleries to ComboBoxes and Patches, although I will add that this is not necessarily everyone's preference.

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

 

 

 

 

View solution in original post

17 REPLIES 17
WarrenBelz
Most Valuable Professional
Most Valuable Professional

Hi @Ashok2 ,

You are submitting a lot of data in both of these - in the first a lot of Patches and in the second two submits and a Patch.

The time taken will be subject to bandwidth available to the user's PC at the time and also the Server load at the other end.

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

 

 

I am able to optimize my second Expression for submission of forms but how can I optimize first patch expression to increase performance ?
WarrenBelz
Most Valuable Professional
Most Valuable Professional

Hi @Ashok2 .

Yes, looking at the second one I now see it is actually three options so it is good you can improve it further.

In the first one, you are doing a Lookup and RenameColumns call to the data source every time you Patch. Assuming you always have less than 2000 items to patch (and you have set the limit to this if necessary) try this - you might possibly have to clean up some commas and brackets, but I am sure you will see the idea.

 

ClearCollect(
   colScopes,   
   RenameColumns(
      Scopes,
      "ID",
      "ID1"
   )
);
UpdateContext(
   {
      vValue:
      LookUp(
         Scopes,
         ID=ID1
      ).Status.Value
   }
);

ForAll(
   colScopes,
   Patch(
      Scopes,
      LookUp(Scopes,ID=ID1),
      { 
         awrWFInProgress:true,
         Status:
         {
            Value:
            Switch(
               vValue,
               "Submitted", "Supported by Manager",
               "Supported by  Manager", "Supported by L2",
               "Pending with L2","Supported by L2",
               "Supported by L2", "Supported by L3",
               "Not Supported by L2","Supported by L3",
               "Reviewed by L4","Supported by L3"
            )
         }
      }
   )
)

 

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

 

I Tried this but getting error in filter statement  attached is screenshot

Filter(
Scopes,
Scope_1.AllItems,Checkbox3_1.Value
),
"ID","ID1"
)

WarrenBelz
Most Valuable Professional
Most Valuable Professional

Hi @Ashok2 ,

Sorry slight flaw in my logic. Do you have less than 2000 items in your list?

 

Yes it less then 2000
WarrenBelz
Most Valuable Professional
Most Valuable Professional

OK @Ashok2 ,

I will also amend original post so as to not confuse people reading it - ensure setting is changed to 2000 in Advanced Settings then 

ClearCollect(
   colScopes,   
   RenameColumns(
      Scopes,
      "ID",
      "ID1"
   )
);
UpdateContext(
   {
      vValue:
      LookUp(
         Scopes,
         ID=ID1
      ).Status.Value
   }
);

ForAll(
   colScopes,
   Patch(
      Scopes,
      LookUp(Scopes,ID=ID1),
      { 
         awrWFInProgress:true,
         Status:
         {
            Value:
            Switch(
               vValue,
               "Submitted", "Supported by Manager",
               "Supported by  Manager", "Supported by L2",
               "Pending with L2","Supported by L2",
               "Supported by L2", "Supported by L3",
               "Not Supported by L2","Supported by L3",
               "Reviewed by L4","Supported by L3"
            )
         }
      }
   )
)

- also check second variable - I cannot test it and cannot see your data. I am just trying to minimize the server calls by setting single values that do not require calling the data before Patching each cycle.

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.


yes i am getting error below ID1 , name isnt valid :this identifier recognized and i am also want to patch only items who are checked in check
UpdateContext(
{
vValue:
LookUp(
Scopes,
ID=ID1
).Status.Value
WarrenBelz
Most Valuable Professional
Most Valuable Professional

OK @Ashok2 ,

Without your code to test this on, I am "flying a bit blind" - I normally write "from inside out", testing each component as I go. What I am trying to do is see what can be done once instead of on each Patch. Looking at the complexity of what you are doing now, I believe possibly only the renaming can be done as below. Firstly, below I have not changed any of your code except this and you should now be querying a Collection and not the data source each time.

ClearCollect(
   colScopes,   
   RenameColumns(
      Scopes,
      "ID",
      "ID1"
   )
);

ForAll(
   colScopes,
   Patch(
      Scopes,
      LookUp(
         Scopes,
         ID=colScopes.ID1,
      ),
      { 
         awrWFInProgress:true,
         Status:
         {
            Value:
            Switch(
               LookUp(
               Scopes,ID=colScopes.ID1
               ).Status.Value,
               "Submitted", "Supported by Manager",
               "Supported by  Manager", "Supported by L2",
               "Pending with L2","Supported by L2",
               "Supported by L2","Supported by L3",
               "Not Supported by L2","Supported by L3",
               "Reviewed by L4","Supported by L3"
            )
         }
      }
   )
)

Second thought - not sure this for reasons above, but try this as well

ForAll(
   colScopes,
   Patch(
      Scopes,
      LookUp(
         Scopes,
         ID=colScopes.ID1,
      ),
      { 
         awrWFInProgress:true,
         Status:
         {
            Value:
            Switch(
               colScopes.Status.Value,
               "Submitted", "Supported by Manager",
               "Supported by  Manager", "Supported by L2",
               "Pending with L2","Supported by L2",
               "Supported by L2","Supported by L3",
               "Not Supported by L2","Supported by L3",
               "Reviewed by L4","Supported by L3"
            )
         }
      }
   )
)

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

 

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,020)