data360-harmonize

This skill covers the Harmonize phase of Salesforce Data Cloud, focused on schema harmonization and unification work: Data Model Objects (DMOs), field mappings, relationships, identity resolution, unified profiles, data graphs, and universal ID lookup. It solves the problem of turning ingested Data Lake Objects into a coherent unified data model by giving the assistant clear ownership boundaries (when to handle the task versus delegate to prepare, segment, or query sibling skills) and a disciplined workflow that inspects schema before mutating anything.

It operates through the external community sf data360 CLI plugin against a Data Cloud-enabled org. The documented workflow runs a shared readiness classifier script to check the org is ready for harmonize work, inspects the DMO catalog and identity-resolution list, describes schemas before mapping, creates or reviews mappings (including dry-run mapping to canonical DMOs), and only then runs identity resolution — treating IR runs as asynchronous and verifying results afterward. It codifies high-signal gotchas such as preferring dmo list --all, using query describe or dmo get --json instead of a nonexistent dmo describe command, API-version sensitivity, and ruleset-specific unified DMO names. It references reusable JSON templates for DMOs, mappings, relationships, identity resolution, and data graphs. The operations are standard, org-scoped Salesforce administration; the CLI mutations act on the authenticated org's data model, so changes should be reviewed before running.

The target users are Salesforce Data Cloud administrators, consultants, and data engineers doing unification and identity-resolution work. Use cases include mapping a DLO to a unified DMO, creating an identity-resolution ruleset, inspecting DMO fields before mapping, and diagnosing why unified profiles are not appearing.