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

Re: SharePoint too many lookup columns cause query failure PowerApps

Yes, my next intuitive line of thinking was to create a backdoor Odata connection into CDS using their new Custom Entity options. However, running into problems there as well- I'm currently interfacing with the development team so hopefully I can gain some traction there.

Highlighted
New Member

Re: SharePoint too many lookup columns cause query failure PowerApps

And where's the solution? Of course the above is not a solution. 

Highlighted
Frequent Visitor

Re: SharePoint too many lookup columns cause query failure PowerApps

I agree. There is still no solution for this lookup column threshold issue. The objective of SharePoint is to manage data using the 'one point of truch' approach. Many people that use SharePoint have BIG lists, with MANY lookups, and have also historically used SPD. This approach means having to rebuild all the lists and convert all workflows to Microsft Flow to enable use of PowerApps. This does not seem feasable at all! I dont think MS is listening to the user base here. There are so many complaints about this issue.

Highlighted
Responsive Resident
Responsive Resident

Re: SharePoint too many lookup columns cause query failure PowerApps

Complex column types

by default the 

Created, CreatedBy

Modified, ModifiedBy 

count toward the total.

 

Dates, Choice, Boolean etc

Anything that has multiple data values for a single record

i.e

Person{DisplayName, Emai)l

ITem{Title, Discription}

Choice{Choice1,Choice2,Choice3}

 

Note that Flow now has a View limter which is good.

Highlighted
New Member

Re: SharePoint too many lookup columns cause query failure PowerApps

Hi Everyone, 

 

This solution does not work for Sharepoint online. Can we make similar changes in sharepoint online ? 

If yes then please share a guide. 

 


@Rfla wrote:

Hi, I understand that the below link is related to flow. I am having a similar issue for PowerApps when connection to a SP online list.

 

https://powerusers.microsoft.com/t5/Community-Feedback/SharePoint-too-many-lookup-columns-cause-quer...

 

@carlosag replied in that tread this:

 

Based on the information here:
By default the limit is 8 lookups per list.  As you have seen this limit does not apply to farm admins.  You can change the limit for other users in the Resource Throttling settings of the web application in Central Administration.  But making changes to the resource limit can seriously impact performance.

Now I am wondering if the suggestion above also is related to SP Online?


 

Helpful resources

Announcements
Ignite

Microsoft Ignite

This will be a conference that you do not want to miss!

secondImage

New Return to Workplace

Reopen responsibly, monitor intelligently, and protect continuously with solutions for a safer work environment.

August 2020 CYST Challenge

Check out the winners of the recent 'Can You Solve These?' community challenge!

Experience what’s next for Power Apps

Join us for an in-depth look at the new Power Apps features and capabilities at the free Microsoft Business Applications Launch Event.

Check this Out

Helpful information

Featuring samples like Return to the Workplace and Emergency Response Applications

secondImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Top Solution Authors
Top Kudoed Authors
Users online (3,814)