Skip to main content Skip to complementary content

Disabling the checking of item dependencies in the MDM Repository

Availability-noteDeprecated

About this task

It is recommended that you leave the checking of item dependencies enabled at all times. However, for large projects with a great number of items in the MDM Repository, it may take quite a long time to check their dependencies. In this case, you may want to temporarily disable the checking of item dependencies and perform a dependency check manually when required.

For more information about how to update item dependencies manually in the MDM Repository, see Updating item dependencies manually in the MDM Repository.

To disable the checking of item dependencies in the MDM Repository, do the following:

Procedure

  1. Click Windows > Preferences.
    The Preferences window opens.
  2. Expand Talend , and then click MDM.
  3. By default, the checking of item dependencies is enabled.
    Select the Disable repository dependencies checking check box to disable the checking of item dependencies in the MDM Repository.
  4. Click OK to validate your changes.

Results

If the checking of item dependencies in the MDM Repository is disabled, when you import items into the MDM Repository or save changes to items, there will be no more automatic computation of the item dependencies as well as no more automatic report of potential warnings and errors related to item dependencies in the MDM Problems view.

Information noteNote: With the checking of item dependencies in the MDM Repository disabled, during the startup of the MDM repository, the automatic dependency computation of all items will no longer be performed, and therefore no warnings and errors related to item dependencies will be shown in the MDM Problems view.

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

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!

Leave your feedback here