Skip to main content Skip to complementary content

Customizing the way warnings and errors related to item dependencies are displayed

Availability-noteDeprecated

About this task

In the MDM Problems view, to customize the way warnings and errors related to item dependencies are displayed, do the following:

Procedure

  1. Click the view menu button in the upper right corner of the console.
    Console menu.
  2. Click Configure Content to open the Configure Contents dialog box.
    Content configuration dialog box.
  3. In the Scope area, select an option to narrow the scope of items to be displayed:
    • On any element: all elements are involved.
    • On any element in same project: all elements in the same project are involved.
    • On selected element only: all selected elements are involved.
    • On selected element and its children: all selected elements and their children are involved.
    • On working set: Window Working Set: the working sets selected after clicking the Select... button are involved.
      Information noteNote: A working set refers to more than one project logically grouped together.
    Information noteWarning: Currently, one and only one project is available in Talend Studio. In this sense, the first option, the second option and the last option are equivalent to each other.
    In the Description area, filter the text if needed and select the check boxes of the severities you want to display.
    In the Types area, select the appropriate types of errors or warnings.
    Information noteNote: The two options MDM Dependency and MDM Model are covered by the MDM Problem option, but you are recommended to select either or both of them to show the specific problems related to item dependencies or/and data models.
  4. If needed, click Restore Defaults to restore the default settings. The options and check boxes in the dialog box will be grayed out.
  5. Click OK to validate your changes and close the dialog box.

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