-
Non-selective query against large object type (more than 100000 rows)
Non-selective query against large object type (more than 100000 rows). Consider an indexed filter or contact salesforce.com about custom indexing.
Even if a field is indexed a filter might still not be selective when:
1. The filter value includes null (for instance binding with a list that contains null)
2. Data skew exists whereby the number of matching rows is very large (for instance, filtering for a particular foreign key value that occurs many times)The above error occurs in production where we have approx 138000 records. We have couple of methods to get this rectified like optimizing the query, null check, making the field external id or unique. Somehow the query Threshold value goes out of the limit that is why the query is not selective. Any help would be appreciated.
Log In to reply.
Popular Salesforce Blogs
Salesforce Integration with Acquire - Complete Guide
Customers are the backbone of all businesses; thus, developing strong and healthy relationships with them is important to the success of your business. Maintaining healthy…
4 Ways a Customer Portal Makes Salesforce & WordPress a Winning Fusion
Customer Relationship Management (CRM) is synonymous with the brand Salesforce. It’s the first name that pops up whenever there is any chatter about CRM. They…
Popular Salesforce Videos
Salesforce JMS Integration Using MuleSoft | Salesforce Tutorial
Salesforce JMS Integration. In this video, the following points will be covered - 1. Introduction Learn how to use queues to integrate data in Salesforce.…
Create and Format Derived Measures
In the explorer, you can perform calculations on existing measures and use the results to create a new measure that’s not part of your dataset.…
myTrailhead Product Filters | Salesforce Tutorial Video
Salesforce myTrailhead has now released their next update in product filters. You can now create your own product filters that are relevant to your business…