You need to sign in to do that
Don't have an account?
Jim Gentile
Error: Invalid Data from Remedyforce Application
All,
Remedyforce went live today with an update to Remedyforce.
I am now receiving the following error when attempting to update account names. Has anyone else seen this issue and how did you fix it if you did?
Error: Invalid Data.
Review all error messages below to correct your data.
Apex trigger BMCServiceDesk.AccountTrigger caused an unexpected exception, contact your administrator: BMCServiceDesk.AccountTrigger: execution of BeforeUpdate caused by: System.QueryException: 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): (BMCServiceDesk)
Remedyforce went live today with an update to Remedyforce.
I am now receiving the following error when attempting to update account names. Has anyone else seen this issue and how did you fix it if you did?
Error: Invalid Data.
Review all error messages below to correct your data.
Apex trigger BMCServiceDesk.AccountTrigger caused an unexpected exception, contact your administrator: BMCServiceDesk.AccountTrigger: execution of BeforeUpdate caused by: System.QueryException: 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): (BMCServiceDesk)
You can fix this by either 1) having more filters in the WHERE clause 2) indexing the fields being used in the query as filters(you can have the field as an external field by checking the External ID checkbox when you define that field)