Map view & Address fields

Put your records on a real map. Give a table an Address field (with Google-powered autocomplete on every edit surface, public forms included), switch to the Map view, and each record becomes a pin placed where its address points — clustered when they crowd, one click from the record itself. The address does not have to live on the table being mapped: a booking can be pinned at the address of the property it booked. Add an Address field Open the table, go to its field editor (Edit fields), add a field, and pick the Address type. That's the whole setup. The field stores plain text and behaves like Text everywhere — filters, reports, exports — but every place you edit it offers real address suggestions as you type, so what gets saved is a clean, complete address rather than a guess. Already keeping addresses in a plain Text field? No rework needed: open the field editor, and in that field's row switch its type to Address. Values are stored as text, so the change is lossless — existing addresses stay exactly as written, and autocomplete kicks in from the next edit. Every way an address gets in Once a table has an Address field, addresses arrive from anywhere: • Typing, anywhere you edit — the grid cell, the full record page, and the peek drawer all pop suggestions as you type; pick one and the complete address is filled in. • Public forms — Address fields on a shared form give visitors the same suggestions, so even data collected from strangers comes in clean. • Imports — when you import a spreadsheet, columns named things like Address, Street, or Location are detected and typed as Address automatically, and you can set any column to Address in the import's mapping step. Imported addresses are located on first map load. • The API — Address is a creatable field type in the developer API, and values write like any text field. • RowFold AI — ask "add an address field to Companies" and confirm the proposal; AI-designed tables can include Address fields from the start. However an address arrives — picked from a suggestion, typed by hand, or imported — the map places it the same way. Turn on the Map view Open the table and click + View → Map in the view switcher. If the table has exactly one Address field the map configures itself; otherwise a card asks which field holds the address. Full street addresses, cities, and postcodes all work. That question is never asked only once. Above the map, Pinned by names the field in use and opens the same picker, so a table with two address fields — billing and site, say — can be switched between them whenever you like. 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. Read the map Each record with an address becomes a pin; pins that crowd together collapse into a numbered cluster that spreads out as you zoom. Click a pin to open the record in the peek drawer — edit there and carry on. A status pill above the map keeps count while addresses are being located, and tells you if any address couldn't be found. Records with an empty address simply don't appear. Filters saved on the Map view narrow the pins exactly like they narrow the grid — a map of only your Active customers is one saved filter away. Filter, search, and share the map The Map carries the same toolbar as every other view: Filter, Search, Fields and Share. Filtering drops pins rather than hiding them — the map asks the server only for the records that match, so a map filtered to Status is Active geocodes and plots only those. The filter lives in the URL, so a filtered map is a link you can send. Admins get Save to “…” to make it the view's own filter. As on the calendar and the tree, a condition on a computed field or one that reaches through a link is a grid-only thing and is not offered here. How locating works (and what it costs you: nothing twice) Addresses are turned into coordinates on the server and cached permanently, so each unique address is looked up exactly once — ever. Big tables fill in progressively: the map locates a batch at a time and the status pill counts down until every pin is placed. An address Google can't make sense of is marked not found once and won't be retried until its text changes. Tips • Prefer the Address type over plain Text for new address data — autocomplete keeps the data clean, which is exactly what makes the pins accurate. • Save filters on the Map view to map a slice of the table — territory, status, owner. • City-only or postcode-only values pin fine — you don't need full street addresses for a coverage map. • Before adding an address field to a table that links to one, check whether the map can just travel the link — a column that exists only to make a tool work is clutter on every row and in every export. Good to know • Maps need the operator to configure a Google Maps key; without one the Map view explains itself and Address fields fall back to plain text inputs. • The map plots the 2,000 most recently updated records — older records drop off on very large tables. • An address marked <em>not found</em> stays unfound until you edit its text — fixing a typo makes it a new address and it's looked up again. Who can do what • The Map view lists only workspaces and tables you belong to, like every view. • If the address field is hidden from your role, the map shows no pins — pins would leak the very values the field hides. • The same applies to an address read through a link: you must be able to see every relationship on the route and the field at the far end. A map is never a way around a permission.