How-to Guides¶
These guides cover tasks beyond the standard setup, including building AddressTools into flows, custom components and Experience Cloud sites. They are published on the ProvenWorks website and open in a new page.
Where a topic is already covered in this support centre, the link below points there instead.
Address Blocks and Record Data¶
To configure an address block of your own, see Binding an Address Block and Creating Address Fields.
For moving a Lightning Record Page from the Aura component to the Lightning Web Component, see Switching to the LWC AddressTools Component.
Access¶
For assigning the Permission Sets and licenses in your own org, see Granting User Permissions and Assign User Licenses.
Flows and Automation¶
-
Create a Contact with a Clean Address in a Salesforce Screen Flow
-
How to populate a state value from a US ZIP Code using a Salesforce flow
-
How to: Automatically Populate the Primary County Field based on the entered ZIP Code
For verifying an address whenever a record is saved, see Configure Automated Verification via a Record-Triggered Flow.
PowerSearch Core¶
PowerSearch Core is the address search component for use outside the packaged AddressTools components.
Setup With an LLM Copilot¶
These guides cover driving the setup through an AI assistant rather than the AddressTools Administration pages.
Resolving Specific Problems¶
-
How to: solve "Secure query included inaccessible field" within AddressTools
-
How to: Solve "Address verification returning 'Verified' with a warning symbol"
-
How to: Solve “Country isn’t standardizing to the full name when saving a record with AddressTools
Where a country or state is not stored in the format you expect, check the settings in Enable Standardisation. Where a report does not appear for selection, check the report requirements in Configure Batch Address Verification.
For the errors AddressTools reports on a record, see Common Error Messages.
Note
Article titles are shown as they are published, so some use US spelling. The guides are maintained on the ProvenWorks website and may describe a different version from the one installed in your org.