Is there any built in xDM functionality that allows you to report on data differences between two points in time?
F
Fathia Jama
started a topic
over 2 years ago
Is anyone aware of examples where people have created customised delta reporting? Context is a scenario where we utilise Historisation of our data, we would then like the ability to generate a report that shows changes (NEW/UPDATED/DELETED) between two inputted dates - eg today and 6 months ago.
Best Answer
F
Fathia Jama
said
over 2 years ago
Hi Steve, thanks for your question. Entity-level Historization does not extend beyond showing a single view for a single date/time combo, so unfortunately it wouldn't perfectly fit your use-case. Historization does have a useful function that allows you to see attribute changes organized chronologically under a TIMELINE (pictured below), however, you cannot specify dates.
The recommended approach is to use one of the History tables in the database, and use the data there to construct your report. The Golden History is located in GH<Physical Table Name>. Master History can be found in MH<Physical Table Name>.Below is an example of records in the GH table, and illustrates how changes are tracked. For ID 10003, the first entry is the delta (New), and the proceeding record represents the most recent change (Updated). GX<Physical Table Name> holds deleted Golden members, while MX_<Physical Table Name> holds deleted Masters. Performing a join between the GH and GX table will provide all the changes associated with a specific record.
1 Comment
F
Fathia Jama
said
over 2 years ago
Answer
Hi Steve, thanks for your question. Entity-level Historization does not extend beyond showing a single view for a single date/time combo, so unfortunately it wouldn't perfectly fit your use-case. Historization does have a useful function that allows you to see attribute changes organized chronologically under a TIMELINE (pictured below), however, you cannot specify dates.
The recommended approach is to use one of the History tables in the database, and use the data there to construct your report. The Golden History is located in GH<Physical Table Name>. Master History can be found in MH<Physical Table Name>.Below is an example of records in the GH table, and illustrates how changes are tracked. For ID 10003, the first entry is the delta (New), and the proceeding record represents the most recent change (Updated). GX<Physical Table Name> holds deleted Golden members, while MX_<Physical Table Name> holds deleted Masters. Performing a join between the GH and GX table will provide all the changes associated with a specific record.
Fathia Jama
Is anyone aware of examples where people have created customised delta reporting? Context is a scenario where we utilise Historisation of our data, we would then like the ability to generate a report that shows changes (NEW/UPDATED/DELETED) between two inputted dates - eg today and 6 months ago.
Hi Steve, thanks for your question. Entity-level
Historization
does not extend beyond showing a single view for a single date/time combo, so unfortunately it wouldn't perfectly fit your use-case.Historization
does have a useful function that allows you to see attribute changes organized chronologically under aTIMELINE
(pictured below), however, you cannot specify dates.The recommended approach is to use one of the History tables in the database, and use the data there to construct your report. The
Golden History
is located inGH<Physical Table Name>
.Master History
can be found inMH<Physical Table Name>
. Below is an example of records in theGH
table, and illustrates how changes are tracked. For ID 10003, the first entry is the delta (New), and the proceeding record represents the most recent change (Updated).GX<Physical Table Name>
holds deleted Golden members, whileMX_<Physical Table Name>
holds deleted Masters. Performing a join between theGH
andGX
table will provide all the changes associated with a specific record.Fathia Jama
Hi Steve, thanks for your question. Entity-level
Historization
does not extend beyond showing a single view for a single date/time combo, so unfortunately it wouldn't perfectly fit your use-case.Historization
does have a useful function that allows you to see attribute changes organized chronologically under aTIMELINE
(pictured below), however, you cannot specify dates.The recommended approach is to use one of the History tables in the database, and use the data there to construct your report. The
Golden History
is located inGH<Physical Table Name>
.Master History
can be found inMH<Physical Table Name>
. Below is an example of records in theGH
table, and illustrates how changes are tracked. For ID 10003, the first entry is the delta (New), and the proceeding record represents the most recent change (Updated).GX<Physical Table Name>
holds deleted Golden members, whileMX_<Physical Table Name>
holds deleted Masters. Performing a join between theGH
andGX
table will provide all the changes associated with a specific record.-
Can we reset Matches and run again on match rule change or add a new match rule?
-
"Unmerge" records
-
Turn off match rules to speed up an integration job
-
Can anyone tell me how to load a Fuzzy-Matched entity ... but skip the matching happening auto-magically?
-
Importing CSV in Fuzzy Matched Entity Does Not Trigger Consolidation
-
How can I trigger a "match on child records"?
-
How can I Configure Most Frequent Values in Survivorship Rules?
-
Deterministic or probabilistic matching
-
Machine Learning and AI for matching
-
Prevent loads from replacing values overridden by users
See all 44 topics