Preface
Part 1: Introduction
Part 2: Configuring Hub Console Tools
- Configuring Access to Hub Console Tools
- Implementing Custom Buttons in Hub Console Tools
Part 3: Building the Data Model
Part 4: Configuring the Data Flow
Part 5: Executing Informatica MDM Hub Processes
- Using Batch Jobs
- User Exits
Part 6: Configuring Application Access
Appendix A: MDM Hub Properties
Appendix B: Viewing Configuration Details
Appendix C: Row-level Locking
Appendix D: MDM Hub Logging
Appendix E: Table Partitioning
- Support for Table Partitioning
Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
Appendix G: Glossary
- Glossary of Terms

Configuration Guide

10.4 HotFix 2

Back Next

Rule 12. Delete or Update a Record Version in a Contiguous Base Object

You cannot delete or update a record version that breaks the contiguity of record versions in a contiguous base object.

If the base object property setting does not allow noncontiguous effective periods, rule 12 ensures the following MDM Hub behavior:

An effective period that breaks contiguity cannot be deleted.

Any change to the effective period of a cross-reference record that breaks contiguity cannot be saved.

The following image shows cross-reference records with contiguous effective periods before and after a version of the cross-reference record is deleted:

Rename Saved Search

Table of Contents

Configuration Guide

Configuration Guide

Rule 12. Delete or Update a Record Version in a Contiguous Base Object

Rule 12. Delete or Update a Record Version in a Contiguous Base Object