Table of Contents

Search

  1. Preface
  2. Using the Designer
  3. Working with Sources
  4. Working with Flat Files
  5. Working with Targets
  6. Mappings
  7. Mapplets
  8. Mapping Parameters and Variables
  9. Working with User-Defined Functions
  10. Using the Debugger
  11. Viewing Data Lineage
  12. Comparing Objects
  13. Managing Business Components
  14. Creating Cubes and Dimensions
  15. Using the Mapping Wizards
  16. Appendix A: Datatype Reference
  17. Appendix B: Configure the Web Browser

Designer Guide

Designer Guide

Handling Keys

Handling Keys

In a Type 2 Dimension/Version Data mapping, the Integration Service generates a new primary key value for each new dimension it inserts into the target. An Expression transformation increments key values by 1,000 for new dimensions.
When updating a dimension, the Integration Service increments the existing primary key by 1.
For example, the Integration Service inserts the following new row with a key value of 65,000 since this is the sixty-fifth dimension in the table.
PM_PRIMARYKEY
ITEM
STYLES
65000
Sandal
5
The next time you run the workflow containing the session, the same item has a different number of styles. The Integration Service creates a new row with updated style information and increases the existing key by 1 to create a new key of 65,001. Both rows exist in the target, but the row with the higher key version contains current dimension data.
PM_PRIMARYKEY
ITEM
STYLES
65000
Sandal
5
65001
Sandal
14
When you run the workflow again, the Integration Service again increments the key. The highest key version contains current dimension data. The target keeps a full history of the item and the order in which the versions occurred.
PM_PRIMARYKEY
ITEM
STYLES
65000
Sandal
5
65001
Sandal
14
65002
Sandal
17

0 COMMENTS

We’d like to hear from you!