Mitigation of issues caused by non-delegable functions

[rkirk2k]

The more I build apps for my organization and teach our users how to build them, it's becoming excruciatingly clear that this is an EXPENSIVE problem. Unless I'm building something that is not business critical, or will have very limited use, the brutal reality is that Power Apps is full of disappointing deficiencies - NONE as frustrating (in my opinion) as how the platform considers anything that has over 2000 records a "LARGE DATA SET" (the default position is 500 records 🙄). 

OK - I'm done venting.  And I'm hopeful that someone with a deeper understanding of the relationship between a SharePoint list and PowerApps happens to feel compelled to read this, and can help me improve the function of a couple of my apps. 

It would be helpful in several cases I have - if I could ensure that PowerApps grabs the MOST RECENTLY CREATED 2000 records.

For instance, my helpdesk app uses search for several critical functions. We've all agreed that the 2000 record limit is not an issue if we can be sure the app always grabs the most recently created records.

(For example, we present a report on tickets closed, by assignee, in the last 30, 60 and 90 days).

CONCERN: As the number of records grows - if PowerApps ONLY always grabs the "top" or "oldest" 2000 records, the non-delegable functions will render our app stupid in very short order. However, if we can be certain the app always grabs the "last" or "newest" 2000 records, we're golden.

Does anyone know...

If we change the configuration of the SharePoint list default view to be sorted in descending order (by Created Date), will the app always grab the top 2000 items from that view? Or, does it ALWAYS for some reason, grab the oldest created items?

Another question I have is regarding using a delegable function to do this, like in the following formula...

You see the delegation warning on the Search function where I'm using a text input box called "AdmSrchActiveTixTextInput" to search the "Title" field.

My question: Since I've done a sort first (which IS delegable), will this always grab the NEWEST 2000 records BEFORE it executes the SEARCH function?

(If so, for the requirements of my customer, the delegation issue in the Search function would not be a problem)

Thank you for any feedback or knowledge you can share!

[SebS]

@rkirk2k 

The order You set SharePoint list will not matter to Power Apps it use ID to pull records and ignore any set up in the List.

if it comes to your function i think best practise is to pre filter first and than place outcome to not delegable function in Your scenario it should look like this

With(
     { 
      PreFilter: YourFilterHere 
     },

Search(
        PreFilter,
        Control.Text,
        "Title",
        "Description"
    )

)

this will make sure all the time the 2000 records are records You looking for until the pre Filter is effected by Delegation 🙂