In Power Apps, the word is * * Delegate * * or * * Delegation * *.

Power Apps sends commands directly to * * Data Source (Data Source) * * instead of pulling all data into the app and filtering / processing it.

---

# # Why Delegation?

* Power Apps have restrictions on retrieving data to process within the app (e.g. 500 or 2,000 records limit).

* If you do not use delegation, the app will load too much data, making it slow and may not complete.

* If there is a delegation, the app will send queries such as * Filter, Sort, Search * directly to SQL Server, SharePoint, Dataverse or other Data Source → Get the specific data required

---

# # Delegation working example

* ✅ 'Filter (SharePointList, Status = "Active")'

→ Power Apps sends a query to SharePoint, filters the data at Status = Active, and sends it back only to the required one.

* ❌ 'Filter (SharePointList, Left (Title, 3) = "ABC")'

→ The 'Left ()' function does not support delegation, the app will load all the data and then filter itself (slow / incomplete risk)

---

# # Words to know

* * * Delegable * * = Function / command that can be sent to Data Source to process

* * * Non-Delegable * * = Functions / commands that Power Apps must process locally (may not complete)

* * * Blue Warning (blue mark) * * In Power Apps Studio, it warns if the code used does not support delegation.

---

# # Brief summary

* * Delegation is a mechanism by which Power Apps send query to Data Source to reduce load and complete data * *

Try to write a formula using the * Delegable * function with the active Data Source to avoid incomplete data problems or slow apps.

---

Training courses

https://analyst-development.net/Course/Schedule