Data 360: Salesforce CRM Data Stream Refresh Errors due to Missing Field or Object

When a CRM data stream fails to refresh, check for an exception in the Refresh History section by clicking the error icon in the Status column. If no details are in the popup, click the Download Log link for more details.

The Resolution steps in this article relate to errors similar to the following examples.

INVALID_TYPE or "Object Is Not Supported" Example

"Invalid extractor job query found. [{\"message\":\"FieldName, FieldName FROM ObjectName LIMIT 1 ^ERROR at Row:1:Column:634sObject type 'ObjectName' is not supported. If you are attempting to use a custom object, be sure to append the '__c' after the entity name. Please reference your WSDL or the describe call for the appropriate names.\",\"errorCode\":\"INVALID_TYPE\"}]"

INVALID_FIELD or "No Such Column on Entity" Example

"Invalid extractor job query found. [{\"message\":\"FieldName, FieldName, FieldName, FieldName ^ERROR at Row:1:Column:4162No such column 'FieldName' on entity 'ObjectName'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.\",\"errorCode\":\"INVALID_FIELD\"}]"

An INVALID_TYPE error indicates an issue accessing the CRM object. An INVALID_FIELD error code indicates the deletion of a field on the object or a loss of access to a field due to permission changes. The field name and object name are listed in the exception as highlighted in bold.

Note: INVALID_FIELD refresh exception only lists one field/column. If this error is caused by the deletion of multiple fields on the object, see the Using Audit Logs to Troubleshoot section below for details on how to identify the deleted fields.

Confirm Object and Field are not Deleted

As these refresh errors can be caused by a field or object deletion, confirm you are able to see both the object and the field in the org.

Note: if the CRM data stream is created using an external org connection, you will need to login to that org to check these details.

Go to Setup and click Object Manager.
Search for the object mentioned in the exception.
If the object is present, open it and then click Fields and Relationships.
Search for the field mentioned in the exception.
If the object and field are present, proceed to Review Data 360 Salesforce Connector Permission Set section.
If the field in the exception is no longer present, follow the steps in Disable a Data Stream Field to disable the corresponding data stream.
Follow the steps and suggestions in Refresh the Data Stream.
- If a successful refresh does not occur after disabling the data stream field, review the details in Find Additional Deleted Fields in Audit Logs to check if there are other deleted fields.

Review Data 360 Salesforce Connector Permission Set

The access Data 360 has to objects in a connected org is determined by the Data 360 Salesforce Connector permission set, which is assigned to a system user called Platform Integration User.

Follow the steps in Object and Field Permissions for Salesforce CRM in Data 360 in the connected org, to confirm that the Data 360 Salesforce Connector permission set still has Read, View All Records and View All Fields permissions for the object listed in the exception. This access is required to create the data stream. If these permissions were removed for the object in the exception after the data stream was created it will result in refresh errors.

If you are seeing an INVALID_FIELD exception and the field listed in the error is a Lookup field, confirm that the permission set still has access to the object referenced by the Lookup field. For example, if the exception states "No such column 'ContactId' on entity 'Case'" then confirm the permission set still has Read, View All Records and View All Fields permissions for the Contact object.

If any required permissions are missing for the object in the exception or its related objects, update the permission set to grant the missing permission. Then follow the steps and suggestions in Refresh the Data Stream. If no permissions are missing review the steps in Confirm if the Data 360 Salesforce Connector Permission Set was removed from the Platform Integration User.

Using Audit Logs to Troubleshoot

Search View Setup Audit Trail in Quick Find in Setup to see changes in your org. If the CRM data stream is created using an external org connection, you will need to check the audit trail in the connected org. Download the audit trail logs and check for changes on the date the errors started in the data stream's Refresh History.

Find Additional Deleted Fields in Audit Logs

If you have confirmed via the steps in Confirm Object and Field are not Deleted that the field mentioned in the exception was deleted but disabling the field on the data stream did not resolve the refresh errors, filter for logs with "Deleted custom field" or "Permanently deleted custom field" in the Action column to check what other fields were deleted on that date. If the audit logs show that multiple fields were deleted, followed the steps in Confirm Object and Field are not Deleted to disable all deleted fields. Then follow the steps and suggestions in Refresh the Data Stream.

Confirm if the Data 360 Salesforce Connector Permission Set was removed from the Platform Integration User

If you did not identify any deleted fields and do not see any missing permissions on the Data 360 Salesforce Connector permission set, check for audit logs indicating the removal of the Data 360 Salesforce Connector permission set from the Platform Integration User. The Action column will contain the follow text:

"Permission set Data 360 Salesforce Connector Integration: unassigned to user Platform Integration User (UserID: [005XXXXXXXXXXXX])"

Note: For deployed orgs that haven’t been updated recently, the Data 360 Salesforce Connector permission set is listed as Salesforce CDP Salesforce Connector Integration, Customer Data Platform Salesforce Connector Integration, or Customer 360 Audiences Salesforce Connector Integration. If logs indicate the following the Platform Integration User has had the permission set removed you will generally see all CRM Data Stream erroring. Follow these steps to reassign the permission set to this system user:

Login to the org with an admin user (e.g. a user with System Administrator profile assigned).
On the upper right corner, click on the Setup icon. Then click on Developer Console.
In the Query Editor tab on the bottom run the following query to get the ID of the Data 360 Salesforce Connector permission set in your org:
1. SELECT Id FROM PermissionSet WHERE label = 'Data 360 Salesforce Connector'
Click on Debug and then Open Execute Anonymous Window.
Add the code from the snippet below to the Enter Apex Code popup.
1. Replace USER_ID with the 005 ID of the Platform Integration User in the audit logs e.g. "Platform Integration User (UserID: [005XXXXXXXXXXXX])".
2. Replace the PERMISSION_SET_ID with the Id returned by the query in 3a.
Click on Execute button to assign the permission set to the user.

PermissionSetAssignment psa = new PermissionSetAssignment(AssigneeId = 'USER_ID', PermissionSetId ='PERMISSION_SET_ID');
insert psa;

Follow the steps and suggestions in Refresh the Data Stream.

Refresh the Data Stream

Click the Refresh button on the data stream to refresh the data stream. If there are a large number of records being ingested from the object in CRM, allow 1-2 hours for a refresh to complete successfully.