What was said
What this says
As at Fri 9 Oct 2026Paul Rigby sent a sample extract with the double-counted jobs highlighted and asked how BG-Demo will handle them. Callie Brennan said she will keep one row per job reference and not switch on the refresh until checked.
Ask: Paul wanted to know how the duplicates would be handled. Callie confirmed the job reference is the key field and the repairs connector stays off until she has checked the sample row by row.
Customer view: Paul was brief and direct, with a clear concern that counts match the housing system report. Callie's answer addresses it.
Next: Callie will send the check result and setup note early next week, then agree a first load date.
The thread
Updated 9 Oct 26Messages
- Callie Brennan 18 Oct 2024 08:49Hi Paul, Thanks for your time on the call. Here is where we landed, so we both have it in writing: - the job reference is the key field for repairs, and I will map everything else against it - the repairs connector stays switched off until you have sent me a sample extract - I will write up a setup note for the repairs source and send it to you What I need from your side is the sample extract with a handful of the double-counted jobs flagged, so I can check how the duplicates appear in the source before we load anything. Thanks, Callie
- Paul Rigby 18 Oct 2024 10:58Callie, Sample attached. Job ref attached for each of the ones that are counted twice, highlighted in the sheet. Same job ref, two rows, different timestamps. That is all I can tell you from my side. Any update on how you will handle it? Paul
- Callie Brennan 18 Oct 2024 11:14Paul, Thanks, that is exactly what I needed. Two rows against one job reference is something I can deal with in the mapping: I will keep one row per job reference and hold the other out, so your repairs counts match the housing system report. I will not switch on the refresh until I have checked that against your sample, row by row. I will send you the result and the setup note early next week, and then we can agree a date for the first load. Thanks, Callie On 18 Oct 2024, at 10:58, Paul Rigby wrote: > Same job ref, two rows, different timestamps.