Project Count Mismatch in Reports
Ticketclosed
Ashwell Mercer Interiors · Project Count Mismatch in Reports
Sunil found project counts in the brain lower than the source system. Kate identified the reporting view returned stale data due to source system lag, not a BG-Demo issue, and recommended querying the base table instead.
What happened
What this says
As at Fri 9 Oct 2026Sunil found project counts in the brain lower than the source system. Kate identified the reporting view returned stale data due to source system lag, not a BG-Demo issue, and recommended querying the base table instead.
Problem: Sunil's report showed fewer projects in the brain than in the source system. Handling: Kate checked the nightly refresh (ran on time), then diagnosed the root cause: the reporting view on the source side had stale data due to materialization lag, not a BG-Demo issue. She advised querying the base table directly for current counts.
Details
Updated 9 Oct 26Trail
created · Sunil Kapoor 31 Mar 2026 10:38Hi, I'm building our monthly report and I'm seeing a discrepancy. The project count in the brain is lower than what's in the source system. I've checked the sync logs and nothing obvious stands out. Could there have been a refresh issue, or is this something on our side?- Public reply · Kate Ormerod 31 Mar 2026 17:36Hi Sunil, I've looked at this morning's refresh, it ran on time and completed successfully. Let me check the source system to see if there might be a configuration issue on the connector. Can you give me a rough count of how many projects you'd expect to see versus what the brain is showing?
- Internal note · Kate Ormerod 1 Apr 2026 10:09Sunil's reporting source is a view built on top of the main table. During the refresh, the view returned stale data, there's a lag in the source system's materialization. Confirmed with Sunil that the view is now current. No issue on our side.
- Public reply · Kate Ormerod 1 Apr 2026 11:52I've worked this through and found it, the view you're querying hasn't fully refreshed on the source side. That's common when views are built on moving data. You might want to build your monthly report directly from the projects table instead, which will be fully up to date. I can talk through the setup if that helps.
- Public reply · Sunil Kapoor 1 Apr 2026 14:49Thanks, that makes sense. We'll adjust our reporting logic to use the base table instead of the view. That should sort it.
- Public reply · Sunil Kapoor 1 Apr 2026 15:11One more thing: once we switch to the base table, will the numbers line up with our finance system's project list, or is there a data mapping issue we need to handle?
- Status change · 27 Apr 2026 23:59