- This topic is empty.
- 04/05/2012 at 9:35 am #4849
Please check your lookup threshold value in Central Administration->Manage Web Application, select your web application and go to General Settings-> Resource Throttling (in the ribbon). Please remember that a people group and workflow status fields count as lookup fields.
You can increase the list view lookup field threshold number and monitor your SharePoint environment for any anomalies (CPU utilization, slow response, etc).
Also please note that even you don't include the lookup fields in the Display Fields of the qListView they're still included in the qListView.
If you have any questions please let me know.
- 04/05/2012 at 9:50 am #6250
- 01/24/2013 at 4:26 am #4076
I have a qlv which is connected to a list that had 4 lookup columns. When I added a fifth to the list, I got the message below. I had not added this new field to the qlv, simply navigated to the page after adding the field.
The following error occurs: The query cannot be completed because the number of lookup columns it contains exceeds the lookup column threshold enforced by the administrator.
Once I removed the field from the list, the message went away and I was able to see the qlv. Is there an issue with the number of lookup columns that a list may have when using qlv?
- 01/24/2013 at 4:26 am #6251
Out of the box Sharepoint views are not constrained the way qListViews are. Instead, OOTB views only complain if the view (not the list) references too many lookup columns.
Are there any plans to modify the way qListViews are implemented so that the lookup limit is less of an issue, similar to OOTB views? If not, many of our applications will require complete redesigns to move from 2007 to 2010 unless we drop our use of qListViews; the Throttling limit would have to be increased beyond what is feasible from a performance standpoint.
For example, maybe provide a way to create a qListView based on an existing OOTB view?
You must be logged in to reply to this topic.