cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Error: The query cannot be completed because the number of lookup columns it contains exceeds

Hi guys,

 

I'm currently running into the following error in PowerApps....

 

First, the error in SP designer makes it seem like it's coming directly from PowerApps.  I pretty sure it has to do with some limitation with Sharepoint and lookups.  

Error_In_PowerApps.png

My team working on Flow was trying to test but PowerApps now throws this error and doesn't allow any of the data from the list to display.  

Lookup_Error.png

 

 

Aside from undoing the "test Flow" what can we do solve for this error?  I guess first is for me to understand where and why the error throws.  Then next possible solutions to workaround this apparent limitation.  The error mentions "enforced by the administrator" could this just simply be for them to increase a limit then all is well?  

 

Referenced: https://blog.portiva.nl/2018/07/04/microsoft-flow-get-item-from-list-with-more-than-12-lookup-column...

 

Thanks,

-Sidney

1 ACCEPTED SOLUTION

Accepted Solutions
v-monli-msft
Community Support
Community Support

Hi @Anonymous,

 

 

SharePoint has lookup column threshold of 12 for now. But please notice what is said here:

https://blogs.msdn.microsoft.com/spses/2013/12/02/sharepoint-20102013-list-view-lookup-threshold-unc...

"Note : The List view Lookup Threshold has been revised to Default of 12 in SharePoint 2013 , after applying the June 2013 CU update. http://support.microsoft.com/kb/2817414

Any new Web-Application created will have List View Lookup Threshold set to Default =12 , While the values on Existing Web-apps needs to be modified Manually ."

 

This applies to SharePoint online too. Lists created before this timeline in SharePoint online will share the List View Lookup Threshold set to Default =8. Lists created after this timeline in SharePoint online, will have List View Lookup Threshold set to Default =12. 

 

With on-premises SharePoint, these throttles and limits can be changed on the Resource Throttling page in Central Administration. But on SharePoint online, increasing the List View Threshold is not permitted

 

Hope this could help.

 

Regards,

Mona Li

Community Support Team _ Mona Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

13 REPLIES 13
v-monli-msft
Community Support
Community Support

Hi @Anonymous,

 

 

SharePoint has lookup column threshold of 12 for now. But please notice what is said here:

https://blogs.msdn.microsoft.com/spses/2013/12/02/sharepoint-20102013-list-view-lookup-threshold-unc...

"Note : The List view Lookup Threshold has been revised to Default of 12 in SharePoint 2013 , after applying the June 2013 CU update. http://support.microsoft.com/kb/2817414

Any new Web-Application created will have List View Lookup Threshold set to Default =12 , While the values on Existing Web-apps needs to be modified Manually ."

 

This applies to SharePoint online too. Lists created before this timeline in SharePoint online will share the List View Lookup Threshold set to Default =8. Lists created after this timeline in SharePoint online, will have List View Lookup Threshold set to Default =12. 

 

With on-premises SharePoint, these throttles and limits can be changed on the Resource Throttling page in Central Administration. But on SharePoint online, increasing the List View Threshold is not permitted

 

Hope this could help.

 

Regards,

Mona Li

Community Support Team _ Mona Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

I am not even using any lookup field in my list why am i getting this error in powerapps?

There is no solution. You start out with 4 out of the box columns, created, created by, modified, modied by. So you actually then only have 8 columns left. Then if you use People or Group Columns, those are also classified as lookup columns. Then if you have used SharePoint Designer, those Workflow Status columns are also recognised as lookup columns. I have seen so many posts, where the answer is marked as 'Solution', which is absolutely not true. This lookup column threshold limit is EXTREMELY limiting when building even a slightly complex solution. 

@Michelle thanks for sharing this.

 

I've just encountered the same issue, and the realization that we are limited in complex/lookup columns is not good and that notion seems crazy. There should be no limit, or at least a high threshold, to Person fields added or else we are basically limited within PowerApps to only make apps that involve a small group of people instead of an app that could potentially involve a much larger group of individuals in a more complex org.

 

I hope this is something the team is working to increase.

@v-monli-msft when is the next increase above 12 expected?

schuess3
Kudo Commander
Kudo Commander
G99
Post Prodigy
Post Prodigy

@LukeC @Anonymous @schuess3 @Michelle @npokhrel123 

 

Hi All, not sure if you all got passed your issue, but I too have just faced the same problem, but feel I have a work around.

 

If I change my person columns to 'single line of text' type in my SPO list, and in PowerApps, I create a variable Set VarUser User().FullName);

 

I then use this variable on my fields which are in fact single line, this should resolve my issue on lowering the amount of Person or Group type fields i'm using in my SPO list, not sure if this will help you guys?

This needs to be fixed in PowerAutomate. They need to add a "Limit Columns by View" to "Update Item" so users can create more efficient queries and create views with just the fields they want to modify thus reducing the amount of lookup columns by not including them in the view. This would be similar to "When an item is created or modified" where they ask for the site, list then view to limit the columns.

I solved this. The solution is to add a view in SharePoint that only contains the columns needing to be updated/modified. Then in Power Automate you add that view and that resolves the issue.

Helpful resources

Announcements
PA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

MBAS Attendee Badge

Claim Your Badge & Digital Swag!

Check out how to claim yours today!

secondImage

Are Your Ready?

Test your skills now with the Cloud Skill Challenge.

secondImage

Demo Extravaganza is Back!

We are excited to announce that Demo Extravaganza for 2021 has started!

MBAS on Demand

Microsoft Business Applications Summit sessions

On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks

Top Solution Authors
Top Kudoed Authors
Users online (74,639)