Standard DMOs

This documentation is available as a developer preview. Documentation isn’t generally available unless or until Salesforce announces its general availability in documentation or in press releases or public statements. All commands, parameters, and other information is subject to change or deprecation at any time, with or without notice. Don’t implement functionality in production with these commands or tools.

Data model objects (DMOs) organize and harmonize your data in Data 360. They’re categorized into standard (std__ prefix) and legacy (ssot__ prefix) types.

When you deploy a new data bundle, standard DMOs have the following traits:

  • No auto-replacement: If an ssot__ DMO already exists, it won’t be replaced by an std__ DMO.
  • Identical performance: They work exactly like legacy DMOs, supporting all the same queries, operations, field types, and relationships.
  • Environment flexibility: They’re data space agnostic, meaning they function consistently across all your different data environments.
  • Fixed configuration: They’re non-editable; you can’t modify API names or primary keys.

Standard and legacy DMOs may appear identical in the UI, but can have different field names or field name capitalization. Fields may have been added to standard DMOs to extend the functionality of frozen legacy objects.

View the list of available objects below:

Standard DMOs can be used in the same way as standard DMOs. They support all standard operations including:

  • Data queries and filtering
  • Field access and manipulation
  • Relationship navigation
  • Integration with file-based data kits