web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Why groupby not a Dele...
Power Apps
Unanswered

Why groupby not a Delegable

(1) ShareShare
ReportReport
Posted on by 207

I have building a power apps which has a order history pages and all the record a saving in dataverse. I was trying  to use the  groupby function to group the order line level which is over 2000 record. I know there have some overcome solution but the performance was terrible. I have building powerapps over a year but still not sure why the there have so many limit when i building the app. I hope it will have any function can replace the groupby function and no need to face the delegable problem 

Categories:
I have the same question (0)
  • Drrickryp Profile Picture
    Super User 2024 Season 1 on at

    @abc3 

    Unfortunately GroupBy() is not delegatable but if you can pre-filter your table down to less than 2k. It will work. Dataverse allows views that can be filtered and sorted. Perhaps you could see if that can work for you.

  • poweractivate Profile Picture
    11,078 Most Valuable Professional on at

    @abc3 

     

    As @Drrickryp said, GroupBy is not delegable to any data source of any kind. 

    You may check here for the reference:

    Non-Delegable functions

    Note that the list above is not exhaustive. There may be other non-delegable functions not specifically listed in the reference above. Sometimes it depends on what data source you are using, but GroupBy is not delegable to any data source in Power Apps currently.

     

    ClearCollect and Collect are other notable functions that are not delegable. Note that even if you don't get the yellow triangle delegation warning, that does not necessarily mean that all parts of your functions are delegable. The only way to be sure, is to set the data row limit to a very low number like 1, perhaps temporarily during development only. If you get only 1 record when you should get way more during testing, then you may have used a non-delegable function somewhere. After you have finished developing, set the data row limit back up to the maximum, 2000, especially if you will be making use of non-delegable functions intentionally, expect to be using it on records pretty close to 2000 in number, and need the data row limit to be at 2000 in the actual finished app.

     

    You should try what @Drrickryp said to use pre filtered and sorted views. You can also try other techniques like getting everything down to 2,000 records or less with other delegable functions first, and using the GroupBy only on the output Table that already has 2,000 or less records

     

    See if it helps @abc3 

  • takolota1 Profile Picture
    4,974 Moderator on at

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 717 Most Valuable Professional

#2
Michael E. Gernaey Profile Picture

Michael E. Gernaey 329 Super User 2025 Season 2

#3
Power Platform 1919 Profile Picture

Power Platform 1919 268

Last 30 days Overall leaderboard