'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Power Apps Lookup Column Threshold Error in SharePoint
Question details
The user needs to understand and resolve the lookup column threshold error encountered in Power Apps and Power Automate when connected to a SharePoint library.
- Product
- SharePoint, Power Apps, Power Automate
- Device & OS
- not provided
- Scenario
- Running Power Apps or Power Automate flows that query a SharePoint list containing multiple Lookup and Person/Group columns.
- Observed behavior
- Power Apps and Power Automate report that the SharePoint library exceeds the lookup column threshold, even when the visible count of lookup columns appears within the allowable limit.
Before troubleshooting, map out all the columns in your SharePoint list, noting that 'Person or Group', 'Lookup', 'Workflow Status', and 'Managed Metadata' columns all contribute to the strict lookup threshold.
Audit and Optimize Your SharePoint List Schema
Identify all columns that count towards the lookup threshold and remove or convert unnecessary ones to resolve the error.
SharePoint has a strict database limitation on how many lookup-type columns can be queried simultaneously. This limit applies to the underlying schema, meaning even if a view hides these columns, Power Apps may still attempt to load them and trigger the error.
Navigate to your SharePoint list or library, click the gear icon in the top right, and select 'List settings' or 'Library settings'.
Manually count all columns categorized as 'Lookup', 'Person or Group', 'Workflow Status', and 'Managed Metadata'. Ensure the total number does not exceed 12.
If you have 'Person or Group' columns used only for static reference (without needing active directory integration), delete them and replace them with standard 'Single line of text' columns.
Remove any legacy or unused lookup columns from the list schema to bring the total count well below the threshold limit.
Create Specific Views to Minimize Query Complexity
Adjusting SharePoint views can sometimes help mitigate threshold errors during specific Power Platform queries by explicitly limiting the columns retrieved.
Consult the Power Apps Community for Specialized Assistance
If recent service changes triggered the error despite no schema modifications on your end, escalate the issue for specialized Microsoft support.
Enhance Your Productivity with WPS Office
While SharePoint and Power Apps manage your backend workflows, analyzing the resulting data exports requires a powerful spreadsheet tool. WPS Office provides a free, lightweight, and highly compatible alternative to Microsoft Office for all your document and data management needs.
- 1. Download the Software: Visit the official WPS Office website to download the free installation package for your operating system.
- 2. Install WPS Office: Run the downloaded installer and follow the simple on-screen instructions to set up the software.
- 3. Open Your Data: Launch WPS Spreadsheet to instantly open, edit, and analyze your SharePoint .csv or .xlsx exports.
Frequently Asked Questions
What exactly counts as a lookup column in SharePoint?
In SharePoint, any column that pulls or references data from another source counts towards the lookup limit. This includes standard 'Lookup' columns, 'Person or Group' columns, 'Managed Metadata' columns, and 'Workflow Status' columns.
What is the lookup column threshold limit in SharePoint Online?
The default lookup column threshold in modern SharePoint Online is typically set to 12. If a query attempts to fetch more than 12 of these specific column types simultaneously, the system aborts the operation to protect database performance, resulting in an error.
Why did my Power App suddenly trigger a threshold error when it was working fine previously?
Microsoft occasionally rolls out backend service updates that enforce data limitations more strictly. If your list was already operating right at the threshold boundary (e.g., exactly 12 lookup-type columns), a minor backend system change or an automatically added metadata column could tip it over the limit.
Can I increase the lookup column threshold in SharePoint Online?
No. In SharePoint Online, the lookup column threshold is a hard limit set by Microsoft to ensure shared server database stability. You cannot modify it. You must optimize and reduce your list schema to resolve the error.
