When running a CRM Analytics Dataflow that includes an Augment node, the job may fail with the following error:
"Something went wrong while executing node augment_Node: Can't find dimension Dimension_Name in update dataset"
This error occurs when the dimension specified as the key field in the Augment node does not exist in the dataset being referenced. The most common cause is that the key field is entirely null across all records in the source object. When a field contains no data, the CRM Analytics Dataflow sfdcDigest node does not create that dimension in the dataset — resulting in the Augment node failing because the key it needs does not exist.
Example: If an Augment node is configured to join on the ParentAccountId field, but no records in the Account object have a value in ParentAccountId, the sfdcDigest node will not include this field in the dataset, and the Augment node will fail.
This error means the key dimension used in the Augment node is missing from the dataset, typically because the source field is entirely null. Choose one of the following options based on your business context:
If the relationship field should contain data but is currently empty, create or update at least one record in Salesforce to populate the key field with a meaningful, non-null value.
Once at least one record has data in the field, the sfdcDigest node will include the dimension in the dataset, and the Augment node will run successfully.
If the key field is entirely null, it likely means your org is not using the relationship that the Augment node is designed to join. In this case, removing the Augment node (and updating or removing any downstream nodes that depend on its output) is the recommended resolution.
To remove the Augment node safely, review the Dataflow definition JSON and identify all nodes that reference the Augment node's output. Update or remove those dependent nodes before deleting the Augment node. Then run the Dataflow to confirm it completes successfully.
000386882

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.