Recovery Manager for SharePoint Premier Edition
Migration Manager for Sharepoint
Server Administrator for SharePoint
Migration Suite for SharePoint
Migrator for SharePoint Online
We are running SP 2010 and Quick Apps 6.3. We have a list containing 11,000+ rows, which exceeds the list view threshold. Field F1 is indexed.
Adding a CAML filter on F1 in a qListView works great - all data displays as expected.
However, using qSelector and qListView, the error "The attempted operation is prohibited because it exceeds the list view threshold enforced by the administrator." is displayed when the page initially loads. Subsequent F1 selections work as expected. Even going back to the initial value (the first value) gives successful results. It's just the initial load of the page that gets the error.
Without going into extreme detail, a similar issue exists when using s qMultiSelector, this time on a document library containing over 5000 rows. The error message displays when the page initially loads. Subsequent selections of the second selector work as expected. (Both selectors are indexed.) In addition, the error message displays whenever the first selector is changed. And, again, subsequent selections of the second selector work as expected.
The same queries are successful when using qListView and CAML filters.
Is there a workaround for this? (Besides doing the queries during the window when operations exceeding the list view threshold are allowed.)
Thank you for any help you might be able to provide.
If the result is over the threshold, this exception will be thrown, this exception is not thrown from the web part, it is from SharePoint. It cannot be overcome without using the CAML to narrow the items.
I have a question about your scenario, if the list has so many items, the qSelector should have a long dropdown items, does it make scense?
The result is not over the threshold. The qSelector is limiting the results. The list is over the threshold, but the results being returned are not.
This error occurs only on the initial load of the page. If a different selector is chosen, the page displays successfully. If the original selector is then selected again, the page displays as expected. It is only on the initial load of the page that the error occurs.
Does another field possibly need to be indexed?
There are only approximately 20 values for F1. The data is spread fairly evenly across the F1 values. We would never expect anywhere close to 5000 results to be displayed.
Are you using the another selector to pass the parameter to the qSelector? If the exception just exist in the initial load, I think the qSelector doesn’t receive the parameter at the first time?
As your description, I think you have set the correct index in the list. I suggest you can try to use the qMultiSelector if you are using two qSelectors in the page.
If you don’t mind, can you give me the screenshot of the full page?
Sorry, am I misunderstand your scenario? The exception is thrown form qListView? Or qSelector? If form qListView, I think you can try to uncheck the “Show Empty Selection” option in qSelector(under the “Selection” section) to let the qSelector to select the first option in the initial load of page, then the qListView can receive the parameter at the first time.
The error is thrown in the qListView web part. It doesn't matter if I have "Show Empty Selection" turned on or off. It happens upon initial entry to the page.
I have attached 3 screen shots. Each page consists of 3 sections:
The first screen shot is the initial display of the page. There are errors in the 1st (as expected) and 3rd sections (not expected).
The second screen shot is after I selected a different Vendor Cage. The 3rd section displays as expected.
The third screen shot is after I re-selected the initial Vendor Cage. The 3rd section displays as expected.
Why does the qListView associated with the qSelector throw an error when the page is initially displayed?
Did you open a subcase for it? If yes, we will handle it by subcase. And will update the result once the case is closed.
I have confirmed that is a bug. Fortunately, this has been fixed in v6.5. that release is coming soon…
Is a subcase a ticket? We do have a ticket open with Dell Support.
Do you know when v6.5 will be available?
The planned RTM date of the 6.5 is 15th, July.