Table of Contents


  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Add a Record Version

Add a Record Version

You can add a version of a record that is effective for a new period.
If you enable contiguity of records in the base object, the
ensures that the record versions have contiguous effective dates. The
extends the effective period of the record version that is adjacent to the record version that you add to maintain contiguity.
Configure the staging table column to add new record versions and C_REPOS_TABLE column to ensure contiguity of record versions.
To add record versions during a load batch job, configure the following settings:
  • TIMELINE_ACTION. Set the value of the TIMELINE_ACTION staging table column to
    . When you set the property to
    , the
    MDM Hub
    can add new record versions. The TIMELINE_ACTION column is mapped from the corresponding landing table column.
  • TIMELINE_FILL_ON_GAP. Ensures that contiguity between the effective dates of record versions is maintained when you add new record versions. Set the property in the C_REPOS_TABLE of the Operational Reference Store or in the Staging Table properties of the Hub Console. If set to
    , when you can add a new record version to the base object, the
    MDM Hub
    maintains the contiguity between effective periods of record versions. If set to
    , the
    MDM Hub
    rejects any addition of record version that breaks the contiguity between effective periods of record versions. The default is


We’d like to hear from you!