Sometimes data streams used by Marketing Cloud Next will fail to refresh and you may notice the following symptoms:
Viewing the error for Data Stream Status
One of the more frequent causes is due to missing field or objects. The error looks like No such column 'FieldName' on entity 'ObjectName'. For Marketing Cloud Next, this is typically a result of one of the following scenarios.
The quickest fix would be to undelete the field in Setup -> Object Manager.
If that's not possible (if the field has been permanently deleted), then you will want to recreate the field with the same API Name. Please note that Salesforce automatically appends '__c' to the Field Name to create the API Name of any custom field. So if you are dealing with an error that states No such column 'Test__c' on entity 'ObjectName', then when creating the field in Setup -> Object Manager, you must only put Test in the Field Name. Once you save, Salesforce will automatically append '__c' and produce 'Test__c' as the final API Name.
Another option is to use the Disable a Data Stream Field feature to disable the corresponding data stream field if it is no longer needed.
If an admin changes the Field Name of a field in Setup -> Object Manager, this will alter the API Name of the field. The quickest fix would be to change the Field Name back to the original field name.
If that's not possible, then you will need to create a new field with the same API Name (similar to the above section).
Another option is to use the Disable a Data Stream Field feature to disable the corresponding data stream field if it is no longer needed.
The Data Cloud Salesforce Connector permission set drives the visibility that Data Cloud has into your Salesforce CRM data. Double check that this permission set has the proper visibility to the field or object (read only is sufficient).
Sometimes features or other licenses in CRM unrelated to Marketing Cloud Next introduce standard fields to the CRM objects used by Marketing Cloud Next. These fields are by default added to the DLOs during the data kit deployment, especially for data kits like the Sales Data Kit that uses widely used CRM objects like Lead, Contact, Accounts, etc.
At a later date, you may find that the features or licenses are turned off or removed from your Salesforce org, which will in turn remove those standard fields from your CRM objects. This will also produce the same No such column error because if the field is not there in CRM, it isn't possible for Data Cloud to query it. Some sample fields that have been observed commonly are:
To resolve this issue, you will want to use the Disable a Data Stream Field feature to disable the corresponding data stream field if it is no longer needed.
Check out this knowledge article for more detailed specific Data Cloud content on this subject.
003962315

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.