Loading

Dataflow warning: 'The dataflow was completed, but the node didn't augment any columns'

Publiceringsdatum: Apr 30, 2026
Beskrivning

Impact of Augmenting on Null or Mismatched Key Fields

 

When performing an Augment Transformation, fields from the right dataset are added to records in the left dataset based on matching values in a set of key fields. If any of the key fields are entirely null or if there are no matching values then the augment will not return any field values from the right dataset, rendering the augment ineffective.

The dataflow will complete successfully, but the anticipated enriched data will not be available in the dataset. A warning message will alert you to what might be perceived as missing data. This warning will appear for each Augment node that has a null key or resulted in no matches.
 
Depending on if the augment that did not match results was a LookupSingleValue or LookupMultiValue, the warning message will be as follows:
  • LookupSingleValue  - If the Augment node is configured as LookupSingleValue, you will see the following warning in dataflow.

The dataflow was completed, but the LookupSingleValue node didn't augment any columns. Either the node didn't find any matches, or a join key contains only null values.

  • LookupMultiValue  -  If the Augment node is configured as LookupMultiValue the warning will instead read as below.

The dataflow was completed, but the LookupMultiValue node didn't augment any columns. Either the node didn't find any matches, or a join key contains only null values.
 

NOTE: This is not a Dataflow Failure. This does not prevent the dataflow from completing. This message is only to alert you to the potential data issues of a no-match or null Augment.

Scenario 
For example your Opportunity dataset relies on an Augment node that pulls Region data from the Account object, using Id of Account as the join key. If the Account Id field is null for some Opportunity records — for example, because those opportunities were created without an associated account — those Records will not be enriched with Region data. The dataflow completes successfully, but the warning appears to alert you that the Augment node returned no results for those records.
Lösning

Interpreting and Resolving the Warning for Templated App users

Note: If the affected Dataflow is part of a templated app, then the augment may be the result of values in system fields or objects, or for features that are not in use in your implementation. In this case, the warning typically can be ignored.
 

To determine which augment(s) were impacted, expand the dataflow in the data monitor. Look for any augment nodes with this warning.

Examine the impacted augments and decide how to address this based on the following:
 
Do your users depend on the augmented fields from the right hand side dataset being available?
  • Yes:
The source data and specified join keys will need to be corrected to allow the augment to produce enriched results. Ensure that the values of the key fields from the source data have matches. Ensure that the join keys used have meaningful values that survive any prior transformations (Filters, Augments, Slices, etc.).
  • No:
If you anticipate the data and keys to produce meaningful results in the future, ignore the warning.
If you do not expect the data and keys to ever produce meaningful results, remove the augment.
  • Unsure:
Identify all dashboards that depend on the augmented dataset. Use the dashboard inspector to understand which fields are being queried. If the augmented fields are being used, follow "Yes". If the augmented fields are not being used, follow "No".
 

 

Knowledge-artikelnummer

000383227

 
Laddar
Salesforce Help | Article