Introduction to the Is Address Check
The Is Address check asserts that every value in a text field is a postal address carrying the parts you require, such as a road, a city, a state, a country, or a post code. Use it on free-text address columns that downstream systems need to parse.
This section is the complete guide to the check. The Deep Dive covers the definition, properties, and full evaluation semantics, explains how anomalies are reported, walks through production examples, and collects best practices; the How-tos are step-by-step tutorials for creating, editing, and deleting a check; the API page documents the payload for programmatic use; and the FAQ answers the most frequent questions.
Next Steps
-
How It Works
The complete reference: definition, field scope, the required labels, parsing semantics, NULL handling, filter behavior, and coverage.
-
Anomaly Reporting
The anomaly messages the check produces, what the numbers mean, Source Records highlighting, and Custom Anomaly Description.
-
Examples
Three production scenarios with sample data, anomaly messages, and the SQL equivalent of what the check evaluates.
-
Best Practices
Guidelines for choosing required parts, handling international data, pairing rules, and keeping the signal clean.
-
Permissions
The team permission each action needs: view, create, edit, archive, restore, and delete.
-
Create a Check
Step-by-step tutorial for creating an Is Address check with the parts an address must carry.
-
Edit a Check
Step-by-step tutorial for changing the required parts, or adjusting the filter, coverage, and organizational properties.
-
Delete a Check
Step-by-step tutorial for archiving a check and deleting it permanently.
-
Troubleshooting
Common problems with international formats, missing parts, NULLs, and anomaly reporting.
-
API
Payload shape and field notes for creating an Is Address check programmatically.
-
FAQ
Short answers to questions about required parts, international addresses, NULLs, and anomaly reporting.