The filter operator is a negative operator such as NOT EQUAL TO (or !=), NOT CONTAINS, and NOT STARTS WITH. The queried values exceed the system-defined threshold. Typically, a custom index isn’t used in these cases. You can’t create custom indexes on formula fields that include invocations of the TEXT function on picklist fields. A custom index can’t be created on these types of fields: multi-select picklists, currency fields in a multicurrency organization, long text fields, some formula fields, and binary fields (fields of type blob, file, or encrypted text.) New data types, typically complex ones, are periodically added to Salesforce, and fields of these types don’t always allow custom indexing. Salesforce Support can add custom indexes on request for customers. When the Salesforce optimizer recognizes that an index can improve performance for frequently run queries, fields that aren’t indexed by default are automatically indexed. Custom fields that are marked as External ID or Unique. RecordType fields (indexed for all standard objects that feature them). Audit dates (CreatedDate and SystemModstamp fields). Foreign keys (lookup or master-detail relationship fields). Primary keys (Id, Name, and OwnerId fields). 
The following fields are indexed by default. Also, the selectivity threshold is subject to change.Ĭustom Index Considerations for Selective SOQL Queries In some circumstances, for example with a query filter that is an indexed standard field, the threshold can be higher. 
The selectivity threshold is 10% of the first million records and less than 5% of the records after the first million records, up to a maximum of 333,333 records. The performance of the SOQL query improves when two or more filters used in the WHERE clause meet the mentioned conditions. A query is selective when one of the query filters is on an indexed field and the query filter reduces the resulting number of rows below a system-defined threshold. To avoid this error, ensure that the query is selective. 
Developers receive an error message when a non-selective query in a trigger executes against an object that contains more than 200,000 records. To avoid long execution times, the system can terminate nonselective SOQL queries. For best performance, SOQL queries must be selective, particularly for queries inside triggers.
0 kommentar(er)
