The View generator page helps flatten Address Validation result tables into a view in your own schema.
Use it after running a bulk Address Validation job. The generator scans address result tables in the app's RESULTS schema, discovers available fields, and creates CREATE OR REPLACE VIEW SQL that selects the fields you choose.
Address results can contain nested VARIANT columns such as components, metadata, match_info, and result_json. View generator lets you turn those nested paths into columns that are easier to query, join, export, or use in downstream reporting.
MYDB.MYSCHEMA.ADDRESS_VALIDATION_VIEW.Field selection is organized by these tabs:
| Tab | Description |
|---|---|
| Core & Address | Core fields such as job ID, record ID, validation status, plus standardized address fields. These are selected by default. |
| Components | Parsed address component fields discovered in the result data. |
| Metadata | Metadata fields discovered in the result data. |
| Match Info | Match detail fields discovered in the result data. |
| Error & Debug | Error fields and optional raw VARIANT fields for troubleshooting. |
The Core & Address tab contains Core Fields and Address Fields sections. The Error & Debug tab contains Error Fields and Debug Fields sections.
The generated SQL follows this pattern:
CREATE OR REPLACE VIEW MYDB.MYSCHEMA.ADDRESS_VALIDATION_VIEW AS
SELECT
job_id,
record_id,
is_valid,
confidence,
address_line_1,
locality,
region,
postal_code,
metadata:dpv:indicator::STRING AS metadata_dpv_indicator
FROM EXPERIAN_DATA_VALIDATION.RESULTS.ADDRESS;
The exact fields depend on your Address Validation configuration and on which optional result data was returned for the selected result table.
Address result tables only