Loading

CRM Analytics Dataflow Error: "Edgemart flatten detected a circular dependency"

Fecha de publicación: May 1, 2026
Descripción

When running a CRM Analytics dataflow, the dataflow may fail with the following error:
"Something went wrong while executing the Flatten_Node node: Edgemart flatten detected a circular dependency in Source_Node."


This error is caused by a record being its own parent in the lookup field that is being processed by the Flatten transformation. The Flatten transformation in CRM Analytics is used to build hierarchical paths (such as role hierarchies or account parent-child relationships). A circular dependency occurs when a record references itself as its own parent.


Example: In Sales Analytics, this may result from one or more Account records where the ParentAccountId field contains the same value as the Account's own Id. The error in this case appears as: "Something went wrong while executing the Flatten_UltimateParent node: Edgemart flatten detected a circular dependency in Add_Fields_To_Account."

Solución

This article explains how to locate and fix the circular dependency error in CRM Analytics dataflows caused by a record being its own parent in the field being flattened.

Locate and Update the Self-Parented Record:

  1. Export a report on the target Salesforce object that includes both the record ID field and the Parent ID field (for example, AccountId and ParentId for Accounts).
  2. Use an external tool such as Excel, Google Sheets, or a SOQL query to identify rows where both columns contain the same record ID.
  3. Update any self-referencing records to remove the circular parent relationship. This can be done through the Salesforce user interface or via the API (for bulk updates).
  4. After updating all self-referencing records, re-run the CRM Analytics dataflow.
Número del artículo de conocimiento

000381991

 
Cargando
Salesforce Help | Article