Olivia Grant

Duplicate customer records in the brain

Ticketpending

Lindqvarn Retail: documents logo Lindqvarn Retail: documents · Duplicate customer records in the brain

Duplicate customer records from Salesforce sync pulling both old and new account IDs. Schema change in customer's org detected; primary key confirmation pending.

Priority normal

What happened

What this says

Current to 11 Oct 26

Duplicate 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.

AI · claude-haiku-4-5-20251001 · 11 Oct 2026

Details

Updated 9 Oct 26
Prioritynormal
Statuspending
Categorydata_quality
Channelemail
First response (min)92
Helpdeskmade from

Trail

  1. Olivia Grant
    internal_note · Olivia Grant 8 Oct 2026 13:33
    Spotted 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.
  2. Linnea Holm
    created · Linnea Holm 8 Oct 2026 17:23
    Hi, 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?
  3. Olivia Grant
    public_reply · Olivia Grant 8 Oct 2026 18:55
    Hi 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
Helpdeskmade from

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

How to ask

Press Ask Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations150
People at customers573
BB-Demo staff48
Calls1,382
Email threads2,122
Support tickets789
Documents850
Deals217
Invoices187
Events49
News items84

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

BB-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Brain is the tool that reads its data.

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

HelpAsk B

Ask B

B-Brain · read-only