- Home
- Skills
- Data & Databases
- Salesforce Data360 Lineage Impact
Works with the AI Agents you already use
Salesforce Data360 Lineage Impact
Trace Salesforce Data Cloud lineage from source contracts to activations to prevent downstream breakages.
Free
Salesforce Data360 Lineage Impact
Example session with this skill installed
Trace the impact of changing the 'Loyalty_Tier__c' field type from String to Integer in the 'Customer_API' source stream.
- Read your context and instructions
- Compiled the salesforce data360 lineage
I have traced the lineage for Loyalty_Tier__c from the Customer_API source through to all downstream activations. The change from String to Integer creates a type mismatch in two Calculated Insights and one Identity Resolution ruleset.
Lineage & Impact Analysis: Loyalty_Tier__c
| Edge ID | Source Object | Destination Object | Edge Type | Expression/Join | Status | Impact |
|---|---|---|---|---|---|---|
| E-001 | Customer_API | DLO_Loyalty_Data | Direct Map | Loyalty_Tier__c | Deployed | Type Mismatch |
| E-002 | DLO_Loyalty_Data | DMO_Individual | Relationship | IndividualId | Active | None |
| E-003 | DMO_Individual | CI_Member_Value | Transformation | AVG(Loyalty_Tier) | Active | Broken Formula |
| E-004 | DMO_Individual | IR_Ruleset_Main | Match Rule | Exact(Loyalty_Tier) | Active | Logic Failure |
| E-005 | CI_Member_Value | Seg_High_Value | Segment | Member_Value > 500 | Active | Data Stale |
Observed Gaps & Risks
Identity Resolution: The IR_Ruleset_Main uses this field for exact matching. Converting to Integer may cause match failures if the source sends leading zeros or non-numeric characters.
Calculated Insight: CI_Member_Value expects a numeric input for AVG(). The current DLO mapping is set to Text; a deployment error will occur unless the DLO schema is updated first.
- Activation: The
Email_Marketing_Targetexpects the legacy String format.
Next steps
- Update
DLO_Loyalty_Dataschema to Integer before deploying source changes. - Refactor
CI_Member_Valueto handle the new numeric grain. - Run
$data360-refresh-orchestrationfor theDLO_Loyalty_Datastream to re-sync historical values.
Connects securely to your tools. The creator never sees your data.
About this skill
Salesforce Data Cloud implementations often break because field changes in the source contract ripple silently through complex DLO to DMO mappings. This skill maps every hop from source API to final activation to ensure schema changes don't crash segments or downstream systems.
What it does
- Lineage mapping traces fields across streams, Data Lake Objects, Data Model Objects, and Calculated Insights.
- Impact analysis identifies downstream consumers like segments and activations affected by schema or logic changes.
- Gap detection compares project manifests against live org configurations to find unverified edges.
- Root cause tracing traverses upstream from null or duplicated values to find the first broken transformation.
- Test scope definition generates a minimal set of refresh actions and quality checks for the affected subgraph.
How it works
- Name a specific asset or field to trace its path across the Data 360 landscape.
- Review the directed graph of edges, including join keys, expressions, and data types.
- Analyze the impact report for proposed changes, identifying potential breakages in identity resolution or CI grains.
- Execute ordered checks to verify live mappings against intended project contracts.
Frameworks & tools
This skill works with Salesforce Data Cloud (Data 360), including DLO, DMO, Calculated Insights, Identity Resolution rulesets, and Activation targets.
Why this beats prompting it yourself
Generic prompts fail to distinguish between a manifest entry and a live mapping. This skill enforces a strict evidence-backed approach that treats formulas and many-to-one resolutions as transformations rather than direct copies, preventing false positives in lineage reports.
Use cases
- Map the downstream impact of a source system schema change.
- Verify that a Data Model Object field is correctly populated from the source contract.
- Plan the safe retirement of a legacy data stream without breaking active segments.
- Troubleshoot why a Calculated Insight is producing null values.
Known limitations
Requires access to project contracts and manifests. Does not execute deletions or replacements automatically; it flags them for manual scope review.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Data & Databases.
Requires project contracts/manifests. Does not auto-execute deletions. Best paired with refresh orchestration and data quality skills for full automation.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 5 days ago
- Free with an Agensi account
- Accounts
Salesforce
- Software
Node.jsSalesforce CLI
Permissions
Allowed Hosts