You are using an older browser that might negatively affect how this site is displayed. Please update to a modern browser to have a better experience. Sorry for the inconvenience!

Require Permission to View Lookup Fields (Critical Update)


Problem:

We have a scenario to assign the record owner to a Queue based on some criteria. The non-admin users are unable to view the value of the Owner field once the Owner field is updated with the Queue.

Root Cause:

We found the root cause for this issue. One of the features of the Spring 20 release (Require Permission to View Record Names in Lookup Fields (Critical Update) causes this issue.

If I logged in as an admin user, I could view the value of the Owner field (as assigned queue name).

If I logged in as a non-admin user, I was not to view the value of Owner field. The Owner label is showing on the page, but the field value is not showing. It is because of the related workflow rule is not triggered for non-admin users. The Owner field value is not showing for non admin user(as below). Please refer the screenshot. 

Workaround:

Salesforce introduced a new permission in Spring 20 release to protect the Salesforce org data by restricting who can view the values of the lookup field.

From Spring 20 release, users must have read access to these records or the View All Lookup Record Names permission in the profile level to view the values of lookup field. This change will be applicable for Lightning and Classic editions. They are applying this feature through the critical update. This critical update also applies to system fields, such as Created By and Last Modified By.

Admins can enable the View All Lookup Record Name permission in custom profiles or permission sets.

Profile Permission:

Critical Update: Require Permission to View Record Names in Lookup Fields