Skip to main content

Managing item dependencies in the MDM Repository

Availability-noteDeprecated

Most items in the MDM Repository are closely related to each other. Whenever you make changes to a repository item, some other items may also be affected. The close relationships between items in the MDM Repository are called dependencies.

When you save changes to items or import items into the MDM Repository, if the checking of item dependencies in the MDM repository is enabled, their dependencies will be updated automatically. If needed, you can update the item dependencies in the MDM Repository manually.

For more information, see Updating item dependencies manually in the MDM Repository.

To reduce the processing time for large projects, you can also disable the checking of item dependencies in the MDM Repository.

For more information, see Disabling the checking of item dependencies in the MDM Repository.

In case of any problems related to item dependencies, Talend Studio provides warnings and errors concerning dependencies so that you can identify the item dependencies more easily and better understand the relationships between items in the MDM Repository.

For more information about how to view the relevant warnings and errors, see Viewing the warnings and errors related to item dependencies in the MDM Repository.

Moreover, Talend Studio allows you to add item dependencies when you export or deploy MDM repository items.

For more information, see Managing data models Managing data models and Deploying repository items to the MDM Server.

Talend Studio supports the following dependencies between items:

Item Dependency
Custom Layout Data Model
Data Model Match Rule
Data Model Role
Data Container Data Model
View Data Model
View Process
Role Stored Procedure
Role Trigger
Role Menu
Role Custom Layout
Role Data Container
Role Data Model
Role View
Role Process
Process Job
Process Data Model
Trigger Data Model
Trigger Job

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!