Loading

Data Sync or Dataflow error: 'Field is not available' in CRM Analytics

Publiceringsdatum: May 21, 2026
Beskrivning

When CRM Analytics runs a data sync, dataflow, or recipe, these processes execute using the Analytics Cloud Integration User. If the Integration User profile does not have read-level visibility for a specific field in a Salesforce object, the sync or dataflow fails with a "Field is not available" error.

This article explains the causes of this error and how to resolve field access issues for the CRM Analytics Integration User.

 

Error Messages


When a single field is not accessible, the error appears as:

"Something went wrong while executing node node_name: Field [Field_Name] is not available. Verify that the field exists and that the Analytics Cloud Integration User profile has Read level access on the field."

When more than one field in the same node is affected, the error appears as:

"Something went wrong while executing node node_name: Fields [Field_Name_1, Field_Name_2] are not available. Verify that the fields exist and that the Analytics Cloud Integration User profile has Read level access on the fields."


Common Causes


This error is generally caused by one of the following:

  • Field Level Security (FLS) restrictions on the Integration User's profile
  • The field is not available in the org (for example, a standard field not included in the org's edition)
  • The field is part of a managed package that the Integration User does not have access to
Lösning

Step 1: Determine the Related Salesforce Object

  • For data sync errors: the node_name in the error message includes the object name, such as "syncOpportunity".
  • For dataflow errors: open the dataflow editor and locate the specified sfdcDigest node to identify the object.

Step 2: Review and Correct Field Level Security

Review the Field Level Security (FLS) for the affected object within the Analytics Cloud Integration User profile. Ensure the profile has Read access on the field listed in the error. See Setting Field Permissions in Permission Sets and Profiles for guidance.

 

Step 3: Check Managed Package Access

 

Review the custom fields on the object to determine if they are part of a managed package. Ensure the Integration User has the necessary permissions and/or licenses to access the managed package containing the target fields. Methods for granting access to managed package components vary — contact the package creator for assistance.



Step 4: Remove Unsupported or Unavailable Fields



If access to the field cannot be granted through the Setup UI, the field is considered unsupported. Remove it from the  data sync configuration or  dataflow definition.



Step 5: Re-Run the Data Sync, Dataflow, or Recipe

Once the field access issue has been resolved, re-run the data sync, dataflow, or recipe.

Knowledge-artikelnummer

000386545

 
Laddar
Salesforce Help | Article