Discussion
Closed · Answered

How do you avoid duplicate data across linked Bases?

QiangDiao Li

Say customers, projects, and content each live in their own Base, with links between them. Would you keep a customer's name and owner in one Base and reference it elsewhere, or copy those fields into each Base? How have you kept updates from drifting apart?

Report
Kelly
Team

I would choose one owner for each fact in Busabase. Keep the current customer name, contact, and account owner in the Customer Base. Projects and content records link to that customer; use a Lookup when those views need to display the current name or owner. A change to the customer record is then read from the same source instead of being copied into every Base.

Copy a value only when it is deliberately a historical snapshot, such as the customer name on a signed contract or the price agreed for an order. Label that field and its date so nobody mistakes it for the current customer profile. For a first pass, give an agent a few sample records and ask it to identify each field's authoritative Base, the links between them, and any fields that truly need snapshots. Which value is currently drifting most often across your Bases?

Report

Your reply

Sign in to join the discussion. Reading is always open; you only need an account to post.

Sign in