When I manually merge 2 records, the GH_table shows only the post merge record. Where do I view the old records?
Best Answer
F
Fathia Jama
said
over 3 years ago
When you have Historization enabled, this is not what you should be seeing. No records are lost from the GH table. When two golden records are merged, the one with the 'losing' ID remains in the table.
What you should see against this row is the B_TOBATCHID column now has a value. It's like a history record, not with an 'end date' but with a 'To Batch'. The 'From Batch' to 'To Batch' indicate between which Integration Batches that record existed as its own golden id.
Try ordering the GH table by the id column and you'll see that it is still there.
When you have Historization enabled, this is not what you should be seeing. No records are lost from the GH table. When two golden records are merged, the one with the 'losing' ID remains in the table.
What you should see against this row is the B_TOBATCHID column now has a value. It's like a history record, not with an 'end date' but with a 'To Batch'. The 'From Batch' to 'To Batch' indicate between which Integration Batches that record existed as its own golden id.
Try ordering the GH table by the id column and you'll see that it is still there.
J
Joao ROSEIRA BORGES
said
4 days ago
As a followup to the above question, I would like to know if the information stored in the GH table is enough to know the precise datetime/batchid where the "old" Golden record ceases to exist in the GD table. Suppose I have the following 2 records in table GH for the old "lost" Golden record UUID1:
from_batchid=BID1 , to_batchid=BID2
from_batchid=BID2 , to_batchid=BID3
Does this mean that the old Golden record UUID1 has been merged during the batchid job BID3 ?
Or could it have been merged in a later batch job that does not add any record to the GH table?
I just want to be sure if there is scenarios where the merge would occur without any further change to the attributes of the old UUID1 Golden record, and so without a trigger to add a new row into the GH table for that "old" golden record.
J
Joao ROSEIRA BORGES
said
3 days ago
after having explored a bit with some examples in a Semarchy productive environment which has lots of merges occurring almost on a daily basis, it seems to me to have concluded the following, but I would like to have your confirmation:
- While a Golden record exists, its last entry on the GH table must have the column B_TOBATCHID = NULL - When a Golden record is deleted because it is merged with another one, its last entry in the GH table is updated with the value of the BATCHID under which the merge occured.
Is that how we can read the information and track the merges of golden records on the GH tables ?
Fathia Jama
When I manually merge 2 records, the GH_table shows only the post merge record. Where do I view the old records?
When you have Historization enabled, this is not what you should be seeing. No records are lost from the GH table. When two golden records are merged, the one with the 'losing' ID remains in the table.
What you should see against this row is the B_TOBATCHID column now has a value. It's like a history record, not with an 'end date' but with a 'To Batch'. The 'From Batch' to 'To Batch' indicate between which Integration Batches that record existed as its own golden id.
Try ordering the GH table by the id column and you'll see that it is still there.
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstFathia Jama
When you have Historization enabled, this is not what you should be seeing. No records are lost from the GH table. When two golden records are merged, the one with the 'losing' ID remains in the table.
What you should see against this row is the B_TOBATCHID column now has a value. It's like a history record, not with an 'end date' but with a 'To Batch'. The 'From Batch' to 'To Batch' indicate between which Integration Batches that record existed as its own golden id.
Try ordering the GH table by the id column and you'll see that it is still there.
Joao ROSEIRA BORGES
As a followup to the above question, I would like to know if the information stored in the GH table is enough to know the precise datetime/batchid where the "old" Golden record ceases to exist in the GD table. Suppose I have the following 2 records in table GH for the old "lost" Golden record UUID1:
from_batchid=BID1 , to_batchid=BID2
from_batchid=BID2 , to_batchid=BID3
Does this mean that the old Golden record UUID1 has been merged during the batchid job BID3 ?
Or could it have been merged in a later batch job that does not add any record to the GH table?
I just want to be sure if there is scenarios where the merge would occur without any further change to the attributes of the old UUID1 Golden record, and so without a trigger to add a new row into the GH table for that "old" golden record.
Joao ROSEIRA BORGES
after having explored a bit with some examples in a Semarchy productive environment which has lots of merges occurring almost on a daily basis, it seems to me to have concluded the following, but I would like to have your confirmation:
- While a Golden record exists, its last entry on the GH table must have the column B_TOBATCHID = NULL
- When a Golden record is deleted because it is merged with another one, its last entry in the GH table is updated with the value of the BATCHID under which the merge occured.
Is that how we can read the information and track the merges of golden records on the GH tables ?
-
Extend a model with new entities or attributes
-
Data types in xDM
-
Effective date on entities
-
Search using wild cards
-
Export a model from production and import on a development environment
-
"Allow Delete" vs "Allow Removal" privileges
-
LOV label in Named Query
-
Select location on a map and save coordinates
-
Is there a way to set up a master-detail relationship on browse mode?
-
Choose Either a Stepper or A Workflow Based on The User Privileges
See all 330 topics