Power Platform Community Forum Thread Details

Hi,

I am building an information relational database for my department at work and I've hit the "lookup column threshold" problem in the first list to use a lot of lookups (both Views and PowerApps). I've redesigned the List so that the number of user-generated lookup, person and date columns is 12 and I no longer have trouble viewing all my columns. However I still get the "lookup column threshold" problem in PowerApps.

Is that because of the system generated lookup columns? (Modified and created dates and persons.) If so is it possible to delete them?

Note that if these are creating the problem, then the actual "lookup column threshold" is only 8.

Sue

Categories:

Building Power Apps

Hi @suelaw1954 ,

Do you mean you have encountered the “LookUp column threshold” error when using SharePoint list as data source?

If so, you are right about that 4 system generated lookup columns (Created/by and Modified/By), according to MS documentation, the following column types are deemed to be "lookup columns" ...

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

Notice:

What classifies as Lookup columns: 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 you could customize up to 8 LookUp columns in SharePoint to avoid the LookUp column threshold error.

Hope this helps.

Best regards,

Community Support Team _ Jeffer Ni
If this post helps, then please consider Accept it as the solution to help the other members find it.