The View Generator 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 EDQ.RESULTS, discovers available fields, and creates SQL that selects the fields you choose.
Address results can contain nested VARIANT columns such as components, metadata, match_info, and result_json. The View Generator lets you turn those nested paths into columns that are easier to query, join, export, or use in downstream reporting.
EDQ.RESULTS.Field groups include:
| Group | Description |
|---|---|
| Core and Address | Job ID, record ID, validation status and formatted address fields. |
| 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 and Debug | Error fields and optional raw JSON fields for troubleshooting. |
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 EDQ.RESULTS.ADDRESS_RESULTS;
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