It will depend on your data model.
If you are using the OOB Identifiers Nested attribute (or an equivalent) to store Source IDs, you can set a Search Filter where Identifiers.ID > 1.
Original Message:
Sent: 09-11-2024 03:04
From: Kulasekaran N
Subject: Understanding the reason for the discrepancy in Profile Counts for a Entity Type on Reltio Platform
Hi Bryant,
Thank you very much for your response-it really helped us understand the discrepancies in the profile counts. I have one more request: is there a way to identify or filter the total number of merged profiles in the Reltio UI?
Thanks & Regards,
Kulasekaran
------------------------------
Kulasekaran N
MathCo
Original Message:
Sent: 09-05-2024 09:06
From: Bryant Barrenechea
Subject: Understanding the reason for the discrepancy in Profile Counts for a Entity Type on Reltio Platform
Hello Kulasekaran,
When you are calculating the count of crosswalks by year, are you checking the individual crosswalks CreateDate of each consolidated crosswalk (of a profile) before adding it to the total?
In the example below, even though you are searching for the crosswalk.CreateDate range, it will return any entity where there is a least one crosswalk that meets the range, in addition to any other consolidated crosswalks whose crosswalk.CreateDate is outside of the range.
For example, to find the profile count for 2019, I applied the following filter: `crosswalk.CreateDate` within "01/01/2019 12:00:00 AM - 12/31/2019 11:59:59 PM," resulting in a profile count of 4,972,446 records.
------------------------------
Bryant Barrenechea
Solution Architect | Professional Services
Original Message:
Sent: 09-04-2024 08:23
From: Kulasekaran N
Subject: Understanding the reason for the discrepancy in Profile Counts for a Entity Type on Reltio Platform
Hi,
I'm conducting an analysis on the Reltio platform to determine the number of profiles loaded or created each year. Our Reltio setup was established in 2019, and records have been flowing in since that year. I'm using the `crosswalk.CreateDate` to determine the count of profiles created annually.
(Note: This analysis is specifically filtered for a single entity type, the "Consumer entity type.")
For example, to find the profile count for 2019, I applied the following filter: `crosswalk.CreateDate` within "01/01/2019 12:00:00 AM - 12/31/2019 11:59:59 PM," resulting in a profile count of 4,972,446 records.
Similarly, for 2020, the filter was `crosswalk.CreateDate` within "01/01/2020 12:00:00 AM - 12/31/2020 11:59:59 PM," yielding a profile count of 822,749 records, and so on until 2024 (up to the current date).
When I summed up the total profile counts across all the years, I arrived at 8,441,349.
However, when I filtered solely for the "Consumer entity type" without any date range filter applied, the total number of profiles displayed in the UI was 8,037,268.
There's a discrepancy of 404,051 records between the two totals. Could you please help me understand why this difference exists? Thanks in advance!
Below is the summary of the profile count analysis:
Year | Profile Count |
2019 | 4,972,446 |
2020 | 822,749 |
2021 | 729,070 |
2022 | 687,515 |
2023 | 739,122 |
2024 | 490,417 |
Sum of profiles across all the years | 8,441,319 |
Total number profiles in UI (for Consumer Entity type, without any date filter applied) | 8,037,268 |
Difference | 404,051 |
------------------------------
Kulasekaran N
------------------------------