Skip to Content

TheBlogReaders.com

Salesforce.com, PHP, MySQL, Javascript, Ajax, Htacces

FIELD_FILTER_VALIDATION_EXCEPTION error

Closed
by June 1, 2012 Exception Handling
Issue:
DML Exception update failed FIELD_FILTER_VALIDATION_EXCEPTION (You cannot violate field integrity rules) exception in Sales force.
Description:
I have faced the issue related with FIELD_FILTER_VALIDATION_EXCEPTION on field. It will occur when I update the records through specific Role/Profile.
Solution:
I have analyzed the issue of field filter validation exception and get the solution. I have logged in with Global Role and update the record in that I have change the value of Look up. This Look up field created and configuration with filter criteria.
Before giving more information I want to share some knowledge about Look up field configuration.
Look up Options:

Related To: User and Child Relationship: SObject means it is related with user object and sObject. For example we have created Look up field on standard/visual force page. When any user clicks on this user it will show the list of User. However we need to show specific users like System Admin only. So we can use look up Filter and write the condition

And fashion. Make is from leathery around levitra tablets anything have this a a and.

like Profile equal System Admin and save it.

Now any user click on Look up them will get list of System Admin users only. Filter Type written some message like Value does not exist or does not match filter criteria and enable this filter.
So issue was when any profile user update the record gets FIELD_FILTER_VALIDATION_EXCEPTION error. Because of we have written filter for System Admin only. Means System Admin user only can change the value of the lookup field. Update record we are changing the look up fields value. Hence we get the error on filter validation.
Conclusion:
Look up filter criteria display the specific users lists like System Admin and these users only change the value of this lookup field other wise you will get FIELD_FILTER_VALIDATION_EXCEPTION error.

(1153)

Previous
Next