How to set up dashboard joins across project and finance data
Ticketclosed
Ashwell Mercer Interiors · How to set up dashboard joins across project and finance data
Sunil asked how to join project and finance data in a dashboard when finance has multiple records per project (revisions, variations). Olivia recommended filtering finance to recent approved records or using many-to-one relationships.
What happened
What this says
As at Fri 9 Oct 2026Sunil asked how to join project and finance data in a dashboard when finance has multiple records per project (revisions, variations). Olivia recommended filtering finance to recent approved records or using many-to-one relationships.
Problem: Sunil needed to combine project management and finance system data but faced duplicates because finance contained multiple records per project.
Handling: Olivia recommended three steps: use project ID as primary key, filter finance records to most recent or approved status, or use many-to-one relationships to preserve detail rows without duplication. Ticket closed 7 Nov 2025 with no further issues.
Watch: Design question resolved with best-practice guidance. Dashboard builder engagement shows value recognition by the customer.
Details
Updated 9 Oct 26Trail
created · Sunil Kapoor 21 Oct 2025 15:34We're trying to set up a new dashboard in the brain that combines data from our project management system and the finance records. The challenge is that the project data has one record per project, but the finance system has multiple records per project, like different budget revisions or variation orders. When we try to join them together, we're getting duplicate records. What's the recommended approach for handling this kind of join without ending up with duplicates?- Public reply · Olivia Grant 21 Oct 2025 17:47Thanks for the question. For joining data across your project and finance systems without duplicates, here's the recommended approach. First, use the project ID as your primary key. It's consistent and clean across both sources. Second, set your finance connector join to filter for the most recent record date per project, or the record status you care about. So if you have budget revisions, grab only the latest approved version. Third, if you need multiple finance records per project, use a many-to-one relationship rather than a join, which preserves both detail rows without duplication. This structure keeps the data clean. Let me know if you need help implementing it or if you run into any issues.
- Status change · 7 Nov 2025 23:59