Why SharePoint and Power Platform Work Together
SharePoint lists and libraries act as a ready-made, permission-aware data store for Power Platform apps and flows. A single standard SharePoint connector, shared across Power Apps, Power Automate, and Power BI, exposes lists and document libraries without any custom API work — an app builder simply picks a site and list from a connector picker rather than writing integration code.
Cricket analogy: SharePoint lists acting as a ready-made data source for Power Apps is like a franchise using the BCCI's existing player registry instead of building a new database of every cricketer from scratch.
Power Apps Canvas Apps on SharePoint Lists
The 'Customize forms' command on a SharePoint list launches a canvas app pre-wired to that list, replacing the default new/edit/display forms entirely. The generated app includes a SharePointIntegration control and form controls bound to the list's columns, so a builder can rearrange fields, add tabs, or apply branding while the underlying list schema stays completely unchanged.
Cricket analogy: Customizing a SharePoint list form with Power Apps is like a coach redesigning the team's warm-up drill sheet — the underlying player roster (list schema) stays the same, but how selection happens changes completely.
Working Within Delegation Limits
Delegation determines whether a Power Fx query executes server-side against the full SharePoint list or only against a locally cached window of records — by default 500 items, configurable up to 2000. Filters and equality checks on indexed columns are generally delegable, while Search() on non-indexed text columns, or filters embedded in nested in-memory collections, are not, silently truncating results once a list exceeds the delegation window.
Cricket analogy: Non-delegable filters hitting the 2000-item cap are like a stadium scoreboard that can only display the first 2000 overs of historical data before truncating — beyond that, the query silently stops looking further.
// Delegable filter — pushed to SharePoint, works beyond 2000 items
Filter(
'Site Requests',
Status.Value = "Pending" && StartsWith(Title, "PROJ-")
)
// Non-delegable — Search() on non-indexed columns runs only against the local delegation window
Search('Site Requests', TextInput1.Text, "Description")Connecting Power BI to SharePoint
Power BI Desktop connects to SharePoint through 'Get Data > SharePoint Online List', importing either a specific list or a whole document library's folder structure directly into a report's data model, ready for visuals, DAX measures, and scheduled refresh once published to the Power BI service.
Cricket analogy: Connecting Power BI to a SharePoint list is like a broadcaster pulling live match statistics from the official BCCI feed to build real-time graphics rather than re-keying scores by hand.
SharePoint list views used by connectors like Power BI and Power Automate are also subject to the 5,000-item list view threshold on large lists unless the query uses an indexed column or a server-side filter — exceeding it returns an error rather than partial data, so large lists intended for reporting should have indexed columns on the fields used for filtering.
Delegation warnings in Power Apps (the yellow triangle) are not cosmetic — if ignored, functions like Search() or filters on non-indexed columns silently operate only on the first batch of records (default 500, configurable up to 2000) rather than the full SharePoint list, producing reports or app behavior that looks correct in testing with small lists but silently loses data once the list grows.
- Power Platform connects to SharePoint through the standard SharePoint connector, available in Power Apps, Power Automate, and Power BI.
- Canvas apps can fully replace a SharePoint list's default forms via the 'Customize forms' Power Apps integration.
- Delegation determines whether a query runs server-side (full list) or client-side (capped, by default 500-2000 records).
- Not all Power Fx functions are delegable to SharePoint; Search() on non-indexed text columns is a common non-delegable trap.
- Power BI can connect to SharePoint lists directly via 'Get Data > SharePoint Online List' for reporting.
- Large lists benefit from indexed columns to keep filters delegable and within the 5,000-item view threshold.
- Delegation warnings in Power Apps Studio should never be ignored in production apps.
Practice what you learned
1. What happens when a Power Apps formula uses a non-delegable function against a SharePoint list larger than the delegation limit?
2. How do you fully replace the default new/edit form of a SharePoint list?
3. What SharePoint limitation applies independently of Power Apps delegation and affects large unindexed lists?
4. Which of these is generally delegable in Power Apps against SharePoint?
Was this page helpful?
You May Also Like
The SharePoint Framework (SPFx)
SPFx is Microsoft's modern, open-source development model for building client-side web parts and extensions that run natively in SharePoint Online.
Workflows with Power Automate
Power Automate replaces SharePoint Designer workflows with cloud-based flows that automate approvals, notifications, and data processing triggered by SharePoint events.
Custom Forms
SharePoint list and library forms can be customized with Power Apps or JSON column formatting to improve data entry accuracy and the end-user experience.
SharePoint REST and Graph API
Two complementary APIs — the classic SharePoint REST API and the modern Microsoft Graph API — let developers read and write SharePoint data programmatically.
Related Reading
Related Study Notes in Programming
Browse all study notesApache Spark Study Notes
Programming · 30 topics
ProgrammingApache Flink Study Notes
Programming · 30 topics
ProgrammingHadoop Study Notes
Programming · 30 topics
ProgrammingSnowflake Study Notes
Programming · 30 topics
ProgrammingApache Airflow Study Notes
Programming · 30 topics
Programmingdbt (Data Build Tool) Study Notes
Programming · 30 topics