Overview

 

If you’ve found that the following error has surfaced within your instance related to LeanData processing, this article will help you understand the issue:

"User does not have permission to Read fields {OBJECT={FIELD}}”,

This error can be found both in the Salesforce Apex view on LeanData jobs and in LeanData Audit logs for impacted records. 

Please note: The Object and Field referenced in the error will vary.

 

Why is this error surfacing?

LeanData is limited to the permissions and restrictions that for each user when routing records.

Whether LeanData is processing via live routing or a scheduled job, the User processing records will need to have visibility into all fields referenced during routing. 

Graph Changes

Most commonly, this error will surface if a User adds field(s) to a graph that the LeanData Integration User does not have visibility to.

While the User that added the field to the graph may have visibility to the field, if the LeanData Integration User does not have the same visibility, the error will surface at the time of routing.

Similarly, if a User schedules a job to run via Routing Scheduler, and the Scheduling User does not have visibility into field(s) that are used in the graph, the error will surface.

User Changes

Alternatively, permissions changes made in Salesforce may also impact visibility into fields that are used in routing. 

For example, when field-level permissions or profile-level permissions are updated, this may inadvertently impact LeanData processing. 

 

What can I do to resolve this?

To resolve this error, you will need to ensure that the LeanData Integration User, or User that initiated a Scheduled Job has a minimum of "Read" permissions to the field called out in the error. 

As an example, the steps below will walk through how to update a Users field permissions if the error calls out the Industry field on the Account Object. 

User does not have permission to Read fields {Account={Industry}}

• Begin by Navigating to Salesforce Setup.
• Open Object Manager and select the Object that is called out in the error.
• Select Fields & Relationships from the menu on the left-hand side, and then select the specific Field that was called out within the error. 

• Once you've selected the correct field, you'll then open Set Field-Level Security.

• On the next page, there will be a list of all Salesforce User Profiles within your instance.

• You will now need to either give full Read and Write privileges to the profile of the Integration User/User processing records, by making the field Visible to their profile.

  • Or, you can select both checkboxes, which will give the User Read-Only permissions. 

• Then, Save your changes. 

Once these steps are completed, the error should no longer surface during routing. 

 

For questions or additional assistance please contact LeanData Support.