Managed Model Concepts
When you onboard a data source with the automated direct load workflow (as described in Onboarding Data with the Automated Workflow) or manually with a Direct Load Step (as described in Onboarding Data with a Direct Load Step), a Managed Model is produced. A managed model is generated, owned, and managed by the data layer that contains the auto-generated or user-created Direct Load Step. If a Direct Load Step query is changed, additional Direct Load Steps are added to the same layer, or the underlying source schema changes, the managed model is automatically updated when the graphmart or layer is reloaded or refreshed. This topic includes important concepts to know when working with managed models.
- Managed Models Cannot be Edited Outside of Direct Load Steps
- There is One Managed Model Per Data Layer
- Deleting a Layer Deletes the Model
Managed Models Cannot be Edited Outside of Direct Load Steps
Though a model that is generated in a Direct Load Step is registered in Anzo and is available for viewing in the Model editor, the model is owned and managed by the layer that contains the Direct Load Step. That means any manual changes made to the model outside of the step, such as from the Model editor, will be overwritten any time the graphmart or layer is refreshed or reloaded. Do not modify managed models except by editing (or adding) Direct Load Step queries. For guidance on editing managed models, see Editing a Managed Model.
There is One Managed Model Per Data Layer
If you include multiple Direct Load Steps in the same layer, they will all update the same model. This functionality can be useful if you want to align the data and generated model across multiple steps. If you have multiple sources that are not intended to align or update the same model, create separate data layers.
Deleting a Layer Deletes the Model
If you delete a layer that includes a managed model, the model is also deleted. Use caution when referencing managed models outside of graphmarts. For example, if you create a dataset and reference a managed model when you select the ontology, the reference will break if the data layer that manages the model is deleted.