Narrator Docs

Validation

All transformations must be validated before they can can be merged to production.

Validating Transformations

Narrator runs a series basic tests to ensure all transformations will process correctly. After you save a transformation, you'll be able to run validation.

These tests check the core assumptions that are used when updating the activity stream, customer, and enrichment tables. When these assumptions fail then the data doesn't process correctly, so the validation step will help catch processing issues before you merge to production.

Successful Validation for an Activity Transformation



Tests

Validation tests required

Test Name

Details

Check for LIMIT Clauses

LIMIT is not used to limit the data output of the transformation

Check for Missing Columns

All required columns are available

Check for NULL Values in Required Columns

activity_id, ts, and activity values are never NULL for Activity Transformations, enriched_activity_id , enriched_ts are never NULL for Enrichment Transformations, customer is never null for Customer Transformations

Check for ID Duplication

activity_id or enriched_activity_id is unique. For Customer Transformations, the test checks that customer is unique.

Note: Additional tests can be manually run on the transformation from the Validation Log tab. More information on the additional validations can be found here.



Troubleshooting tips




Still have questions?


Our data team is here to help! Here are a couple ways to get in touch...

šŸ’¬ Chat us from within Narrator

šŸ’Œ Email us at [email protected]

šŸ—“ Or schedule a 15-min meeting with our data team

Updated 3 months ago



Validation


All transformations must be validated before they can can be merged to production.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.