What happened
What this says
As at Fri 9 Oct 2026Duplicate transaction records in CRM data were caused by two fields being mapped to the same source. BG-Demo corrected the mapping and resolved the issue after the next refresh cycle.
Problem: Duplicate records appeared only in CRM data, affecting transaction search accuracy. Femi reported the same transaction appearing twice.
Handling: Olivia Grant identified a configuration error: two CRM fields were mapped to the same source, creating duplicates on sync. She corrected the mapping and expected resolution after the nightly refresh.
Impact: Data quality issue resolved via configuration fix. No recurring risk indicated from current evidence.
Details
Updated 9 Oct 26Trail
- Public reply · Femi Olatunji 4 Dec 2025 09:04The duplicates are appearing only in the CRM data, not the accounting records. It looks like it might be a syncing issue from our end.
- Internal note · Olivia Grant 4 Dec 2025 10:56Customer reporting duplicate records in CRM data. Femi says it's only in CRM, not accounting. Could be a configuration issue with the connector. Need to check their mapping rules.
- created · Femi Olatunji 4 Dec 2025 12:23Hi support, we're seeing duplicate records in our data. Specifically, when we search for transactions by customer ID, we're getting the same transaction twice. This is affecting our reporting accuracy. Can you help us identify the source of these duplicates?
- Public reply · Olivia Grant 4 Dec 2025 14:47Hi Femi, thanks for reporting this. I've looked at your CRM connector configuration and found the issue. You have two fields being mapped to the same source, which is creating duplicates when the connector syncs. I've corrected the mapping, it should clear up on the next refresh cycle, which runs tonight. Can you check again in the morning and let me know if the duplicates are gone?
- Status change · 15 Dec 2025 23:59