Showing results for 
Search instead for 
Did you mean: 
Level: Powered On

SharePoint lookup column threshold enforced by the administrator.


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

Super User
Super User

Re: SharePoint lookup column threshold enforced by the administrator.

Hi @Akumar ,


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. 



Hope this helps!


Good luck,


Level: Powered On

Re: SharePoint lookup column threshold enforced by the administrator.

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:

Helpful resources


Microsoft Business Applications Virtual Launch Event

Join us for an in-depth look at the new innovations across Dynamics 365 and the Microsoft Power Platform.


Watch Sessions On Demand!

Continue your learning in our online communities.

Power Platform 2019 Release Wave 2 Plan

Power Platform 2019 Release Wave 2 Plan

Features releasing from October 2019 through March 2020


Flow Community User Group Member Badge

Fill out a quick form to claim your user group badge now!


Microsoft Learn

Learn how to build the business apps that you need


Power Platform World Tour

Find out where you can attend!


Webinars & Video Gallery

Watch & learn from the Flow Community Video Gallery!

Users Online
Currently online: 199 members 4,398 guests
Please welcome our newest community members: