Skip to main content Skip to complementary content

Viewing log files for all data records


In Talend MDM Web UI, the Journal page provides a list of log files with descriptions of every event associated with each data record in the MDM hub.

This page is useful if you want to search for changes for all data records based on the data model, the entity, the key of the data record, the source, the operation type, the user name, or the operation time, rather than searching for changes only of a specific data record in the User Journal page.

Before you begin

  • The MDM server is already launched.
  • You have logged in to Talend MDM Web UI.
  • You have selected the data container that holds the master data you want to manage and the corresponding data model against which the master data will be validated.
  • You have been assigned the role with the appropriate user authorization and access rights.

About this task

To view the log files for all data records, do the following:


  1. From the Menu panel, click Browse and then click Journal to open the Journal page.
    Alternatively, from the Welcome page, click Journal.
  2. The page shows a log table, along with various search options. By default, the Data Model list shows the data model you have selected in the Domain Configuration area.
    Select ALL from the Data Model list to display the log files for all data models.
  3. You can limit the search results by using the options in the Search Panel at the top of the page.


    Information noteNote: You can switch between the log table and a timeline view - a design showing a calendar labeled with dates and events labeled on points where they have happened - using the Results and TimeLine tabs.

    In the log table you can see a list of all the events concerning the data records in the MDM hub to which you have access rights. The default column headings show you the following information concerning each data record:

    Column name


    Data Container

    Name of the data container that pertains the data record.

    Data Model

    Name of the data model against which the data record is validated.


    Name of the business entity that pertains the data record.


    The primary key of the data record.

    Operation Type

    Type of operation carried out on the data record: CREATE, UPDATE, PHYSICAL_DELETE, LOGIC_DELETE, RESTORED, or ACTION.

    Operation Time

    Date and time of the operation.


    Name of the source through which the data record modification took place, a Talend Job, the Web User Interface (manually by a data steward), etc.

    User Name

    Login name of the user who made the modification.

    Primary Key Info The primary key information of the data record.
    Information noteNote:
    • If multiple element values are included in the primary key information, they are concatenated using a hyphen (-) character.
    • For an element of float, double, or decimal type, your raw input value is saved in the primary key information and displayed on Talend MDM Web UI.
    • For a multi-lingual element, its raw value is saved in the primary key information and displayed on Talend MDM Web UI, for example, [EN:Product][FR:Produits].
    • It is not recommended to include the value of a foreign key element in the primary key information, since only its raw value can be saved in the primary key information and displayed on Talend MDM Web UI.

    In the log table, you can double-click a row or right-click a row then click View Changes to open the Data Changes Viewer tab.

    On the tab, you can:

    • click the View Update Report button to view the update report details.
    • click the Previous Report button to navigate to the previous event.
    • click the Next Report button to navigate to the next event.
    • click the Open Record button to open a new tab which displays the associated data record.
    Information noteNote: The display of entities or elements defined with multilingual labels varies depending on the locale you selected from the top right corner.

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 – let us know how we can improve!