Map view & Address fields — Pin by an address on a linked table

Most records have no address of their own, and shouldn't. A booking is not at an address — the property it booked is; an order is delivered to its customer; a shift happens at its site. Stored properly the address lives once, on the table it belongs to. So the address picker doesn't stop at this table. Every relationship is an entry you can open: click Property and you are looking at the property's fields, and picking Address there pins each booking where its property is. Keep going if you need to — Deal → Company → Address is a perfectly ordinary answer — and the map labels itself with the route it followed. Nothing is added to your schema. There is no helper column to create and no field copied onto every booking; the address is read through the link when the map loads, so it is always whatever the property says it is today. If the link reaches several records — a company and its contacts, each at a different office — you get a pin for each of them, all opening the same record. Repeated addresses collapse into one pin.