Create a Composed Model Based on a Referenced Model
Use an existing semantic model and extend it to create a composed model. When you create
a composed model it stays connected to the referenced model, and the referenced model remains
the single source of truth. Changes made to the referenced model are automatically added to the
composed model, but changes made to the composed model aren’t pushed to the referenced model.
In Data Cloud, on the Semantic Layer tab, click New Model.
Select Create from Existing Model and then click
Next.
A list of semantic models that you have access to appears.
Select the semantic model to use as the Referenced Model, and then click
Next.
Enter the Composed model information.
Give the model a descriptive name and an API name, and enter an optional description. You
can’t change the API name after the model is created.
Click Create.
After you create a composed model, you can:
Add new definitions to the composed model independent from the referenced model.
Override definitions from the referenced model to customize properties.
Delete the referenced model to remove all its semantic definitions from the composed
model and make it an independent model (a semantic model that's not based on any other
model).
Override Semantic Definitions in a Composed Semantic Model When you create a composed model, the composed model inherits all property definitions from the referenced model. If you change any property definition, the new definition is defined as an override. An overridden property definition is not connected to the referenced model. As such, your overridden property definitions are not changed when the referenced model is updated. Properties without overrides on the other hand, remain connected to the referenced model data source and receive updates from it, keeping it as the source of truth. If you want to return to the original values, you can always revert the override and resume automatic updates.
Override a Field, Data Object, or Calculated Field Property Learn how to override a definition in a composed model. The process disconnects one or more definitions from a referenced model allowing you to keep the custom definition free from updates to the referenced model.
Revert Overrides Learn how to reconnect semantic definitions to an associated referenced model. This action reverts the semantic definition back to the current value of the referenced model. It doesn't delete the composed model.
Add Fields to a Composed Model In a composed model, you can add standard or custom fields that weren’t originally selected in the referenced model. You can edit these fields only in the composed model. They aren’t included in the referenced model.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.