What happened
What this says
Current to 14 Oct 26After loading the Tolmere customer data into the brain, several hundred accounts served by both divisions appeared twice. Olivia asked for a customer mapping to build deduplication rules and escalated the work to engineering.
Problem: Duplicate customer records for accounts served by both Harcastle and Tolmere divisions after integrating Tolmere data. Handling: Olivia identified this as an expected integration challenge and requested a mapping of matching records to build deduplication rules keyed on customer number. She escalated to engineering for technical implementation. Watch: Integration of acquired company data creates data quality challenges that need clear mapping and dedup logic. No follow-up comment shown; confirm dedup was successfully deployed before completion.
Details
Updated 9 Oct 26Trail
- created · Imran Hussain 19 May 2026 09:32After loading the Tolmere customer data, we're seeing duplicate customer records. Several hundred accounts that both divisions served appear twice in the brain, once from Harcastle and once from Tolmere. Each customer appears twice in our dashboards, which is causing problems with queries and reporting. We need to deduplicate them properly.
- public_reply · Olivia Grant 19 May 2026 13:46Hi Imran, That's a great catch, and an expected challenge with the Tolmere integration. To fix this properly, we'll need to set up a deduplication rule based on a unique identifier. For customers, that would typically be the customer number or email. Do you have a mapping of which Tolmere customer records correspond to the Harcastle ones? If you can get me a sample, I can work with our team to build the dedup logic. Cheers, Olivia
- internal_note · Olivia Grant 19 May 2026 15:37Escalating to Felix, needs dedup rules on the customer connector. Customer number should be the key. Imran may have a mapping or we can script it from overlapping addresses and trading names.
- status_change · 2 Jun 2026 23:59