We encountered a situation where we need to assign record ownership to a Queue based on certain conditions. However, after updating the Owner field with the Queue, non-administrative users are unable to see the Owner field value. Further investigation revealed that the issue is caused by one of the features introduced in the Spring 20 release – the “Require Permission to View Record Names in Lookup Fields” critical update.
After assigning record ownership to a Queue based on specific criteria, non-administrative users cannot view the value of the Owner field.
We have identified that the “Require Permission to View Record Names in Lookup Fields” critical update introduced in the Spring 20 release is responsible for this issue. As an administrator, you are able to view the value of the Owner field, which is displayed as the name of the assigned Queue.
the Owner field label is visible, but the corresponding field value is not displayed. This issue is specific to non-administrative users, as the related workflow rule is not triggering for them. Hence, the Owner field value is not visible to non-admin users.
To address this issue, Salesforce introduced a new permission in the Spring 20 release that restricts access to the values of lookup fields. As of this release, users must have read access to the relevant records or have the “View All Lookup Record Names” permission in their profile to view the lookup field values. This applies to both Lightning and Classic editions, and is implemented through a critical update that also affects system fields like “Created By” and “Last Modified By”.
To enable non-admin users to view the Owner field value in this scenario, admins can grant the “View All Lookup Record Names” permission to the appropriate custom profiles or permission sets. This will allow non-admin users with the specified permission to view the lookup field values, including the Owner field value assigned to the Queue.