Catalog Metadata
Data Spaces map to domains in Prizm. A DMO’s category is applied as a semantic tag, and key qualifier fields mark primary keys. Descriptions come from each object’s label and description metadata. Data Source Objects (DSOs) appear only as the origin of a DLO in lineage, not as catalog assets.
Observability Signals
Lineage
Prizm builds native lineage from Data Cloud metadata:- Data Source Object to DLO to DMO to Calculated Insight to Segment to Activation
- Data Transform source to target
Quality and Criticality
- Quality rules. Prizm uses reusable rule templates. Key qualifier fields automatically activate uniqueness rules, and referential-integrity rules are suggested from DMO relationships. You can edit or disable any of them.
- Exceptions. Rows that fail a rule are found with SQL and written to a partitioned Iceberg table, linked to the rule execution.
- Criticality. Each object is scored from its dependencies, volume, metadata and sensitivity, key attributes, and structure. Freshness and usage aren’t part of the score yet.
What Prizm Does Not Collect
Reports and Dashboards aren’t available yet. Prizm doesn’t collect query usage, Data Shares, Data Graphs, CRM Analytics pipelines, or Einstein model execution. Identity Resolution rulesets, Data Streams, Data Actions, and Einstein Studio models are configuration metadata, and Prizm doesn’t run or retrain them.Next Steps
Setup
Create the Salesforce app and connect Data Cloud.
FAQ
Common questions about the Salesforce Data Cloud connector.