How many records are suggested in canvas power apps without effecting performance using standard or premium connectors

[Anonymous]

Hello,

Would like to understand , How many records/items are suggested in canvas power apps without effecting performance using standard or premium connectors?

Is it 2k items , even after following only delegable functions using SharePoint list & indexing in data source , without effecting the app performance or what is the count?

If it does effect the performance , which standard connector is preferred to maintain the app performance?

If not through standard connectors , premium connectors will help here?

Or are we supposed to use model driven app for data more than 2k items rather than canvas app? But customer would like to use only standard connectors for the app.

kindly mention the queries little brief , as can't see any clear MS documents mentioning even after following delegating functions , if there any performance issues.

[WarrenBelz · Accepted solution]

Hi @Anonymous ,

A very broad question, but it is more about Delegable queries (or keeping them that way). SharePoint (standard connector) for instance can hold up to 33 Million records and proving the query is Delegable the performance will be fine. I have many lists over 50k and they work as well as small ones with Delegable queries. One note here is that over 5k records, any fields involved in queries need to be indexed in SharePoint (you can have 20 fields per list). I have a blog on Delegation that may assist you and have found SharePoint will do most things you need as long as you plan your data structure properly.

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.

Visit my blog Practical Power Apps

[Anonymous]

Hello @WarrenBelz thanks a lot for the response , briefing it clearly helps a lot for us. So until delegable functions are used & indexing is done on SharePoint list , no need to worry about the items limit you mentioned (33 Million records )of or performance right?

Based on these I got 2 things to ask , please brief on the same:

1. As you mentioned performance will not effect by following delegations etc. Hope it will not effect based on number of users using the app? Is there any limit on number of users using the app with SharePoint as data source & my data is huge like say more than 5k records?
2. Also as we also have 'Data verse for teams' comes under standard, as this only have 10GB of data provided . How preferable it is to use for large data or mid level or only below 2k records without effecting performance? Also every teams environment in which app is created has only 2GB per environment, How fast does this 2GB data gets filled up(any example) ? Mainly this data source is applied for which scenario's & please mention how many records it can store?

Request you to brief them , as I couldn't find any docs based on performance & data size to maintain the same performance , it would be really helpful for developing choosing right data source.

[WarrenBelz · Accepted solution]

Hi @Anonymous 

For the first item, concurrent users as such are not an issue as they are each running a "local" copy of the app in their browsers. Concurrent queries to the data source would in very large numbers could have impact on performance, but unlikely much unless you have thousands of users. For the second question, unfortunately I use neither Dataverse or Teams with Power Apps, so cannot comment.

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.

Visit my blog Practical Power Apps

[Anonymous]

Hello @WarrenBelz thanks a lot for the quick response & for the helpful info. 

So other than creating indexes in SharePoint list , delegable functions do we have any other thing to follow or any other limitations?

Because I've come across a scenario where if we have flows for our app using lists & if lists have more than 5k items , the flows will not render the info/filter info once the list reaches 5k , we are supposed to perform/follow some actions to render/ filter from the info & this might effect the performance? In which flow scenario's does this happen?   Can you please brief & provide a correct solution on this .

Really appreciate your efforts till now , thanks a lot . Please do mention the above queries as well.

[WarrenBelz]

Hi @Anonymous ,

I have never found any issues with Flows on indexed columns - are you saying you have ?

[Anonymous]

Hello @WarrenBelz not exactly I didn't receive it , but there were articles mentioning like below :

https://tachytelic.net/2020/04/many-ways-get-sharepoint-items-power-automate/

https://alextofan.com/2019/08/22/how-to-get-more-than-5000-item-from-sharepoint-online-in-flow/

 I have come across this concepts of paging, we are supposed to create loops if we have more than 5000 items in list for the flows .

Can you add light on this or you say there will be no issues with flow even more than 5k items in the list? By indexing the columns we want?

 kindly mention, it would be really helpful.

[WarrenBelz]

Hi @Anonymous ,

That is about retrieving more than 5,000 records, not getting a set of records from a list of more than 5,000 items.

[Anonymous]

Okay so you mean, getting/retrieving more than 5000 at one stretch right? In power apps or any where else from SharePoint list.

Thanks again...

[WarrenBelz · Accepted solution]

Hi @Anonymous ,

Yes - the article were regarding Power Automate - you should be able to get over 5,000 in Power Apps, however they are returned 100 at a time in galleries, so a lot of scrolling to get to the end.