What happened
What this says
Current to 11 Oct 26Duplicate customer records from Salesforce sync pulling both old and new account IDs. Schema change in customer's org detected; primary key confirmation pending.
Problem: Linnea reported duplicate customer records from the Salesforce sync with both old and new account IDs for the same customer, affecting dashboard accuracy. Handling: Olivia identified a schema change in the customer's Salesforce org (account ID field mapping changed) and asked Linnea to confirm which field should be the primary key for matching, so the sync mapping can be corrected. Status: pending customer input.
Details
Updated 9 Oct 26Trail
- internal_note · Olivia Grant 8 Oct 2026 13:33Spotted this in the connector logs earlier today, looks like a schema change in their Salesforce org. The account ID field mapping changed recently. Need to check with them which field is the primary key now.
- created · Linnea Holm 8 Oct 2026 17:23Hi, we're seeing duplicate records in the brain for some of our customer accounts. It looks like our Salesforce sync is pulling in both the old and new account IDs for the same customer. This is throwing off our dashboards. Can you help us clean this up?
- public_reply · Olivia Grant 8 Oct 2026 18:55Hi Linnea, I can see the duplicates in the logs. Just so I've got this right: this started after your team made changes to your Salesforce account structure? Can you tell me which field should be the primary key for matching customer records? Once I know that, I can review the sync settings and we can get this sorted. Thanks, Olivia