- Home
- Skills
- Data & Databases
- Salesforce Data360 Model Deployment
Works with the AI Agents you already use
Salesforce Data360 Model Deployment
Reconcile Salesforce Data 360 models, automate DLO-to-DMO mappings, and verify referential integrity.
$11
Salesforce Data360 Model Deployment
Example session with this skill installed
Check the mapping drift for the Contact DLO to Individual DMO and suggest the reconciliation steps.
- Read your context and instructions
- Compiled the salesforce data360 model
I have retrieved the live metadata for the Contact_DLO and compared it against the desired state manifest. I found two unmapped fields and one data type mismatch on the birthdate field.
Data 360 Mapping Reconciliation Report
| Component Type | Object Name | Field API Name | Status | Action Required |
|---|---|---|---|---|
| DLO Field | Contact_DLO | Mobile_Ext__c | Unmapped | Map to Individual.Mobile_Phone |
| DLO Field | Contact_DLO | Birth_Date__c | Conflict | Source is DateTime; Target is Date |
| Relationship | Individual | Party_ID__c | Active | None (Verified ManyToOne) |
| Formula | Contact_DLO | FRM_Hash_ID | Missing | Deploy deterministic key formula |
Deployment Plan
- Update Formula: Deploy
FRM_Hash_IDtoContact_DLOusing the deterministic SHA256 logic. - Correct Mapping: Update
Birth_Date__cmapping to include a type-cast transform toDate. - Add Mapping: Map
Mobile_Ext__cto the targetIndividualDMO. - Verify: Poll status until the mapping state transitions to
ACTIVE.
Next steps
- Approve the field-level diff to generate the deployment manifest.
- Run the preflight check for the
FRM_prefixed formula keys. - Initiate the pilot deployment for the
Contact_DLOupdates.
Connects securely to your tools. The creator never sees your data.
About this skill
Deploying changes to Salesforce Data 360 models manually often leads to mapping drift, broken relationships, and referential integrity failures. This skill automates the planning and verification of DLO-to-DMO mappings, formula deployments, and identity resolution carriers to ensure your data model stays in sync with your source schemas.
What it does
- Automated Mapping Reconciliation: Compares desired state manifests against live DLO/DMO configurations to identify drift or conflicts.
- Formula Deployment: Manages Data Stream formula updates while preserving existing mappings and enforcing deterministic key prefixing.
- Relationship Management: Validates child-parent foreign keys and ensures carrier fields are active before creating
ManyToOnerelationships. - Identity Resolution Logic: Sets up Party Identification records using governed identification types to separate identifier equivalence from record identity.
- Batch Transform Validation: Verifies composite resolution joins and routes ambiguous or unmatched rows to audit outputs.
How it works
- Preflight Audit: Retrieves live metadata for DLOs, DMOs, and existing relationships to produce a field-level diff.
- Manifest Processing: Applies version-controlled formula definitions and mappings while verifying data types and primary key coverage.
- Sequence Execution: Deploys changes in order, ensuring mappings are
ACTIVEbefore dependent relationships or transforms are initialized. - Verification: Inspects referential integrity for orphans or ambiguous matches after the deployment completes.
Frameworks & tools
This skill is designed for Salesforce Data Cloud (Data 360) environments, utilizing the Metadata and Data Cloud APIs for model mutations.
Why this beats prompting it yourself
Standard prompts often ignore the asynchronous nature of Salesforce mapping activations, leading to race conditions. This skill enforces a strict dependency chain where relationships only deploy once carrier fields are verified as active.
Use cases
- Deploying new custom DMO fields and mappings from a version-controlled manifest.
- Troubleshooting broken
ManyToOnerelationships between custom and standard objects. - Standardizing Party Identification carriers across multiple disparate data sources.
- Configuring batch transforms with composite resolution logic and error routing.
Known limitations
Does not support reactive deactivation of standard relationships if the API restricts it. Requires the user to manually trigger the final UI step if API reactivation fails.
Does not support reactive deactivation of standard relationships if the API restricts it. Requires manual UI intervention for specific restricted state changes.
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 any payment.
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
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 5 days ago
Requires
Permissions
Allowed Hosts