Help me understand the 2,000 record max for PowerApps Canvas Apps

[Kirsten2]

I will be connecting PowerApps with data from 10 different tables that will together exceed over 2,000 records. Will that be an issue?

Or is it only an issue to what you can visually see in a gallery, for example, if it is connected to a table that is over 2,000 records? 

Will PowerApps delegation functions be able to read over 2,000 records if in one table? 

Has PowerApps ever crashed due to the amount of data it is connected to?

Many thanks!

[BCBuizer]

Hi Kirsten,

The delegation limit only applies to a single data source, so 2000 records in a single table. 

I'm sure there have been instances where users have asked too much from PowerApps when it comes to data, but the numbers you are talking about seem nowhere near that. Having said that, it all depends on what you actually do with the data. In case you are planning to do a lot of data transformations, that may be challenging....

Perhaps you can elaborate a bit on what you plan to use the app for?

[Kirsten2]

I am building an equipment order application, which consists of about 180 data fields, and about 1,000 equipment parts to choose from. We get about 400-500 orders per year that consists of child tables for the equipment they order per order, which can be about 20 different equipment per order, and a child child table of vendor performance for shipping each of those equipments at different times. Also my boss wants to standardize some of our data fields by linking it to Offices/Programs names, which we do not have a standardize list yet, but I assuming that will exceed 2,000. (I worry also combo boxes just have a 500 item limit to search names, however, from a standardize list.)

Edit: This will be over a 50 screen app with ordering equipment capability, allowing modifications to orders, allowing review of orders, and allowing tracking of orders. Plus it will have export capabilities of order forms, etc. for the customer.

Edit: There is some data transformations with joining different data tables to be viewed in one gallery list (i.e. our customer information and order information are in different tables but needed in one gallery view.) And later in the tracker section, I'll need to join the customer, order, and equipment information. 

[Kirsten2]

I edited my comment for more clarity of scope.

[BCBuizer]

Hi Kirsten,

This all sounds ambitious but you should be fine. 

There are many other ways of selecting items besides comboboxes and even the search functionality in comboboxes can be made delegable (sort of).

The only thing I can say up front is that 50 screens may be a bit much, in which case you may consider having multiple apps for specific tasks.