Lingo - Conflict Detector

The same business term is often calculated differently across dashboards and reports, quietly eroding trust in enterprise analytics. This recipe traces every reporting column back to its source, detects where a single business term resolves to multiple distinct formulas, enriches each conflict with governance ownership context, and automatically raises a project task so the right steward can investigate and resolve the discrepancy.

What you receive

How the recipe works (guided flow)

Step 1 — Reporting Surface
Joins the chart and chartchild tables to build a base inventory of every report column across all dashboards.

Step 2 — Lineage Presence
Flags each report column with whether it has any resolvable upstream lineage, without yet resolving the source.

Step 3 — Term Normalization
Lowercases and collapses separators in each column name into a structural "normalized_term" grouping key.

Step 4 — Usage Impact
Aggregates how many report columns share each normalized term to measure its usage footprint.

Step 5 — Term Candidates
Filters out technical identifiers, keys, codes, and date/time fields to surface genuine business term candidates.

Step 6 — Identifying Criticality
Combines lineage presence, business-term candidacy, and usage count into a single CRITICAL_FLAG per column.

Step 7 — Critical Scope
Narrows the working set down to only the columns flagged as governance-critical.

Step 8 — Immediate Sources
Resolves the single deterministic upstream table and column feeding each critical report column.

Step 9 — Source Signature
Builds a standardized "table.column" source signature for each critical column, marking unresolved sources explicitly.

Step 10 — Formula Conflicts
Normalizes formulas and counts distinct formula variants per term to detect true definition conflicts.

Step 11 — Conflict Details
Pulls every report column contributing to a detected formula conflict, alongside its formula and source signature.

Step 12 — Conflict Details and Governance Roles Associated
Enriches each conflicting column with its owning report's governance roles (owner, steward, custodian) for review.

Step 13 — Summary of Conflicts
Presents the full formula-conflict dataset, joined with governance context, as a reviewable summary.

Step 14 — Identified Conflicts & Task Creation
Builds the final Identified Conflicts table (term, chart, chart child, formula, and steward) and automatically creates a project task per conflict under the "Lingo - Conflict Management" project for governance follow-up.

Step 15 — Conflict Visualization
Computes how many distinct formula variants exist per normalized term and renders a bar chart to prioritize which terms need the most urgent governance attention.

Sample insights (illustrative)

Make sure the following ingredients are available in your workspace:

• Connected datasets are crawled and profiled
• Columns have distinct counts and top values generated
• A project named exactly "Lingo - Conflict Management" must already exist before running this recipe, since the task-creation step maps every conflict to this project by name