Limits of PA: Too much data, even w. Dataverse (Non-delegable functions)

[AgileAlex]

Hey guys,
we are veleoping an application w. PA, combined with Dataverse.

I´ve seen PA´s architecture is limiting the processing of datasets with certain functions at 2.000 records, as seen here & here:
- " Under General, change the Data row limit setting from 1 to 2000." "Because the Search function isn't delegable to the SharePoint data source, Power Apps has to process the records locally, which means first the records are sent from SharePoint to Power Apps. By default, the data source will only return the first 500 records. It isn't the first 500 records that match your formula, but the first 500 records in the data source. In this example, when you add this formula to your gallery, SharePoint returns the first 500 records from the list to Power Apps, and then Power Apps does the search operation locally. If your list contained 5,000 items, the other 4,500 records in your data source aren't processed or displayed. You can increase the default of 500 records to a maximum of 2,000 records in the advanced settings of Power Apps Studio. Under those circumstances, 3,000 records still wouldn't be processed or displayed."

So if I have a function such as ClearCollect, which is is a neccessary function for some developments I just can not use it if I want to process datasets > 2.000 records?
What is the workaround here?
Or is the situation like this (?): If you have records less than 2.000 you can process your data for all functions in PowerApps.
But if you have records > 2.000 you can ONLY use delegable functions, if you want to make sure ALL of your data is processed correcetly. This is because you can not process more than 2.000 records with non-delegable functions and the non-delegable functions can´t be processed by the server (as with delegable functions).
And if you still want to create a proper working application w. PowerApps with more than 2.000 records to be processed, you can not use:

• First, FirstN, Last, LastN
• Choices
• Concat
• Collect, ClearCollect
• CountIf, RemoveIf, UpdateIf
• GroupBy, Ungroup

I would really appreciate a workaround here, since just not using those functions is not a suitable solution for certain usecases.
Thank you.

[Feiteira]

Hi there @AgileAlex ,

You are correct and have done your study 😄

PowerApps gets the default number of rows of 500 with a limit of 2000. This does not mean you cannot get more than 2000 records but you have to do some workarounds, if you really need to have more than 2000.

The good practice is to use mainly Filter(), Search() and Lookup() as mentioned in this article 

https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/delegation-overview 

Can you give us some usecases when you really need to have mroe than 2000 records?