[SalesForce] Content cannot be displayed: Too many query locator rows: 10001

How to show a message/convey to the user that there are more than 10000 records when using StandardSetController?

Do I need to fire a separate SOQL just to count the number of rows and use the LIMT clause in the StandardSetController query to limit the rows? Is there a better way?

Also what is the use of the method getCompleteResult() ? I thought I could use this method to see if there are more than 10000 records in the StandardSet but when there are more than 10000 the page simply errors out with the message "Content cannot be displayed: Too many query locator rows: 10001".

Best Answer

If I take an org with over 50000 Account records and run this snippet, I don't get any errors and I do get the expected output:

ApexPages.StandardSetController controller = new ApexPages.StandardSetController([
    SELECT Id FROM Account LIMIT 50000
]);

system.debug(controller.getCompleteResult()); // false
system.debug(controller.getResultSize()); // 10000

And I also get the expected output if the LIMIT is at or below 10000.

ApexPages.StandardSetController controller = new ApexPages.StandardSetController([
    SELECT Id FROM Account LIMIT 10000
]);

system.debug(controller.getCompleteResult()); // true
system.debug(controller.getResultSize()); // 10000

I tested these with API Version set all the way down to 10 on my Apex Class and 15 on my Visualforce Page, and did not receive an error. Perhaps you open another query locator somewhere else on your page somewhere.

<apex:page controller="Throwaway">
    <apex:outputText value="{!IF(controller.completeResult, 'complete', 'partial')}" />
</apex:page>

<!--
public with sharing class Throwaway
{
    public ApexPages.StandardSetController controller
    {
        get
        {
            if (controller == null)
                controller = new ApexPages.StandardSetController([
                    SELECT Id FROM Account LIMIT 50000
                ]);
            return controller;
        }
        private set;
    }
}
-->

Related Solutions

[SalesForce] StandardSetController List Instatiation and setFilterId

I think utilising the List View UI to allow your users to reuse this part of the platform is a great design decision btw! I've used this approach before and can tell you it does not matter what the original record set you select with your query selector is, so you can in fact use LIMIT 1.

However, unfortunately the StandardSetController will only handle 10,000 rows regardless, check out the documentation for the StandardSetController.getCompleteResult method.

"Indicates whether there are more records in the set than the maximum record limit. If this is false, there are more records than you can process using the list controller. The maximum record limit is 10,000 records."

So at least this method does let you inform the users that the results your showing them are truncated and thus ask them to refine their selection criteria.

If thats not going to be good enough for them or you, then you could utilise the Metadata API to retrieve the ListView definition and roll your own SOQL query. I've recently done this in Java for a DF12 presentation here. If you want to do this in Apex you can also utilise the Apex Metadata API library here. Let me know if you want to this route we could build a sample here together.

[SalesForce] Error: Too many query locator rows: 10001

The way you should really test a batch is by calling Database.executeBatch. Don't call start and execute directly.

You should also test without SeeAllData. You should never use SeeAllData unless it's your only choice. There are many reasons why it's bad practice to unit test against existing data. Unit tests will not perform the same in your sandboxes as your staging/production environments. Your tests will run significantly slower. You have a lot less control over what you're actually testing.

Take a look at Using Batch Apex (specifically the Testing Batch Apex section). You need to make sure you get at most one execute block, which effectively limits you to 200 records.

static testMethod void testMyBatch()
{
    // setup data for your batch to process
    // make sure it's less than 200 records
    // you can only call the execute method once!

    Test.startTest();
        Database.executeBatch(new MyBatch());
    Test.stopTest();

    // assert on results
}

Best Answer

Related Solutions

[SalesForce] StandardSetController List Instatiation and setFilterId

[SalesForce] Error: Too many query locator rows: 10001

Related Topic