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

SharePoint lookup column threshold enforced by the administrator.

Hello,

I am trying to create a list item through MS flow event and i'm receiving below error. any idea ? Its sharepoint online.

 

The query cannot be completed because the number of lookup columns it contains exceeds the lookup column threshold enforced by the administrator.
clientRequestId: e4b095da-0e06-40a3-bea3-7e3dd6656d90
serviceRequestId: 3607c19e-9055-8000-0ff9-10831eaeea9a

2 REPLIES 2
Laskewitz
MVP

Hi @Anonymous ,

 

It looks like your SharePoint list exceeded the 12 lookups limit. Make sure the view you are querying doesn't have more than 12 lookups in it. 

 

get-items.png

Hope this helps!

 

Good luck,

Daniel







Did I answer your question? Mark my post as a solution!


Proud to be a Flownaut!






Michelangelo
Advocate I
Advocate I

Akumar - I ran into this issue just last week. Let me explain:

We discovered this issue not while using Flow, but while using PowerApps, but it's the same issue. Flow, PowerApps, etc. - basically all of MS's PowerSuite Apps can only "talk to" SP Lists with 12 or fewer "Look-up" column Types. 

If you're like me, at first was like wtfmate I only have a couple, like 5, but the reality is different... Here is a quote I found online: "Standard lookup columns, single-value managed metadata, multiple-value managed metadata, single-value people and group columns, and multiple-value people and group columns , Workflow Status , Created by , Modified by ( people ) are obviously counted as lookup columns .

 

Additionally following columns shows on list view also work as lookup columns , Name ( linked to Document) , Link (Edit to edit item) , Name ( linked to Document with edit menu), type ( icon linked to document)"

So, literally, OOtB a SharePoint list already uses up 2 of the possible 12 look-up columns allocated to you because of the "Created By" and "Modified By" columns - which you cannot delete. 

You will need to remove all people-picker columns, managed metadata columns, etc. until you are down to 12 or less for Flow/PowerApps to be able to talk to your SP List. 

The List I was trying to connect to in PowerApps had 14 people-picker columns + Created By + Modified By, meaning I had 16 "look-up" columns, so I had to get rid of 4 of my custom-built people-picker columns to connect to PowerApps. 

 

Here is the article I think I got that quote from: https://powerusers.microsoft.com/t5/General-Discussion/SharePoint-too-many-lookup-columns-cause-quer...

Helpful resources

Announcements
MPA 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

MSFTBizAppsLaunchEvent

Experience what’s next for Power Virtual Agents

See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.

New Super Users

Meet the Power Automate Super Users!

Many congratulations to the Season 1 2021 Flownaut Crew!

Power Platform ISV STudio

Power Platform ISV Studio

ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.

Users online (43,452)