SharePoint Lookup Column Threshold in PowerApps Custom Forms

Introduction

When customizing SharePoint list forms using PowerApps, you may encounter an error stating that the lookup column threshold has been exceeded. This issue often appears even when no custom logic has been added, which can be confusing for developers and users alike.

Example Error

Below is a typical error message seen in PowerApps:

"The query cannot be completed because the number of lookup columns it contains exceeds the lookup column threshold."

In this article, I will explain what the lookup column threshold is, why it occurs, and how to resolve it effectively.

What is the Lookup Column Threshold?

In SharePoint, there is a limit on how many lookup-type columns you can use in a single query or view, and this limit is usually around 12 columns.

Below columns are included in this limit:

Lookup columns
Person or Group columns
Managed Metadata columns

These columns are included as "lookup" because they retrieve data from another source.

What does NOT count as lookup columns?

Below column types do not consider to the threshold:

Single line of text
Multiple lines of text
Number
Yes/No
Date/Time
Choice (standard)
Currency
Hyperlink or Picture
Calculated columns

Why does this error occur in Power Apps forms?

When you customize a SharePoint form using Power Apps, the form uses a below default formula in the Item property:

If(
   IsBlank(SharePointIntegration.Selected),
   First([@YourListName]),
   SharePointIntegration.Selected
)

Even if you do not change this formula, PowerApps tries to get the full record from the SharePoint list. If your list has too many lookup-type columns, this can exceed the lookup column limit and cause an error.

What is the problem?

SharePoint tries to return all columns for that item
If the list contains more than around 12 lookup-type columns
The query exceeds the limit

Result: Error is thrown

Why Indexing Does Not Help?

A common misconception is that indexing columns will resolve this issue.

But the reality is:

Indexing improves performance for large lists (5000+ items)
It helps with filtering and sorting
It does NOT reduce the number of lookup columns in a query

Therefore, indexing does not fix the lookup column threshold error.

How to Fix the Issue

1. Reduce Lookup-Type Columns

Review your SharePoint list and:

Remove unnecessary lookup columns
Reduce the number of Person/Group fields
Simplify Managed Metadata usage

2. Simplify the Form

In PowerApps:

Open the form
Go to Edit Fields
Remove unused fields, especially lookup/person fields

3. Redesign the Data Structure

If the list is too complex:

Split it into multiple lists
Normalize the data structure
Avoid excessive cross-list dependencies

Key Takeaways

The lookup column limit is typically around 12 columns
It applies to queries, not just the list design
PowerApps forms can trigger this automatically
Indexing does not fix the issue
The best solution is to reduce or simplify lookup-type columns

Conclusion

By using this article, you can understand the lookup column threshold and why it becomes more visible when using Power Apps custom forms. This helps you design better and error-free solutions in SharePoint.