Two deliberately separate passes. First, replay any recorded lookup exactly. If there is none, geocode the linked contact's street/city/state/zip and run the same resolve the search button runs — which records it, making the cost one-time per card.
Also called: permit autofill · address prefill · permit check self-populates
- 1permitAddress is built from the linked contact: street, city, state, zip
- 2A state on its own is rejected — it 'would geocode to the state's centroid and pin a random field'
- 3Pass A (restore) needs only the map; Pass B (geocode) needs the county index too, so they are separate effects
- 4A once-only ref stops the geocode re-firing on every identity change
- 5Street is included deliberately because which side of a boundary a build sits on changes the answer
Quoted verbatim in the component: 'any contact that enters the system that has an address — I want that address auto-populated in the permit check section, so they can see the state, county, city… or if it's more of a remote area, a drop pin where their address is, and the respective boxes around it. So that they can see the permit information automatically.' The comment also records the bug this fixed: 'opportunityId was write-only here — used to RECORD a lookup and never to read one back — so a card that had been auto-checked on board load still made the rep retype the address to see what we already knew.' And a hard warning: '⚠️ THEY ARE SEPARATE BECAUSE THE DEPENDENCIES DIFFER, AND MERGING THEM BREAKS A.'
- The rep retypes an address the system already holds
- A card answered on board load still looked unanswered inside
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →