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.
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.
Complex column types
by default the
count toward the total.
Dates, Choice, Boolean etc
Anything that has multiple data values for a single record
Note that Flow now has a View limter which is good.
This solution does not work for Sharepoint online. Can we make similar changes in sharepoint online ?
If yes then please share a guide.
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.
@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?
Fill out a quick form to claim your user group badge now!
Find out where you can attend!
Features releasing from October 2019 through March 2020
The largest Power BI, Power Platform, and Data conference in New Zealand