Promote Quality Checks¶
Promote Quality Checks copies quality checks from one container to another, even across different datastores. This feature helps you reuse existing quality rules without manually recreating them in the target container. This feature is useful when you want to:
- Reuse existing quality checks in another container or datastore.
- Quickly set up quality checks for similar datasets without starting from scratch.
- Standardize quality rules across multiple data stores.
To start it, open the Settings menu on a container and choose Promote > Quality Checks. You can also select checks in a datastore's Checks list and choose Promote from the bulk actions menu.
Note
Archived checks are never promoted. Draft and AI Managed checks are included by default, and the promoted copies are created as Authored checks. Promote As Draft is on by default, so new copies arrive as Draft for you to review and activate. A check that already exists on the destination is updated in place and keeps its status.
Let’s get started 🚀
How It Works¶
The Promote Quality Checks process consists of two main steps:
1. Select Checks¶
Choose which quality checks to promote:
| REF. | FIELDS | DESCRIPTION |
|---|---|---|
| 1. | All | Promotes all quality checks available in the source container, excluding archived ones. |
| 2. | Specific | Lets you manually select individual quality checks from a list. Useful when you only need certain checks in the target container. The Include Draft and Include AI Managed switches, both on by default, control whether those checks appear in the list. |
| 3. | Tag | Promotes all quality checks that match the selected tags, allowing for automated grouping. |
2. Destination Settings¶
Define where the selected checks should be promoted:
| REF. | FIELDS | DESCRIPTION |
|---|---|---|
| 1. | Datastore | The datastore where the selected quality checks will be promoted. |
| 2. | Table | The specific target container (e.g., table) within the datastore where the checks will be added. |
| 3. | Assign additional tags | Lets you add tags to promoted checks to help with categorization and filtering in the target datastore. |
| 4. | Promote As Draft | On by default. Creates the promoted checks as Draft. |
Note
Fields are matched by name when possible. With Promote As Draft on, a check none of whose fields match the destination is created as a Draft with no field assigned. With it off, promoting that check fails.
Example Use Case¶
Scenario
You have two tables in the COVID-19 Data datastore:
-
CDC_INPATIENT_BEDS_ALL – contains all hospital inpatient bed records.
-
CDC_INPATIENT_BEDS_COVID – contains only records related to COVID-19 cases.
The first table already has 12 authored quality checks to verify important fields like hospital_id, report_date, and available_beds.
The second table doesn’t have these checks yet, but it uses the same structure and fields.
Instead of creating all 12 checks again, you promote them from CDC_INPATIENT_BEDS_ALL to CDC_INPATIENT_BEDS_COVID.
This way, both tables follow the same validation rules, saving time and keeping data quality consistent.
Before and After Promotion
| Item | Before Promotion | After Promotion |
|---|---|---|
| Source Table | CDC_INPATIENT_BEDS_ALL (authored checks already exist). | CDC_INPATIENT_BEDS_ALL (unchanged). |
| Destination Table | CDC_INPATIENT_BEDS_COVID (no authored checks). | CDC_INPATIENT_BEDS_COVID (authored checks in Draft status). |
| Check Count | 12 authored checks. | 12 authored checks (copied). |
| Status of Checks | Active in source. | Draft in destination. |
| Benefit | N/A | Saves time, ensures consistency, and avoids manual recreation. |
Visual Diagram¶
graph TD
A[Start] --> B[CDC_INPATIENT_BEDS_ALL Source: 12 Authored Checks]
B -->|Promote| C[CDC_INPATIENT_BEDS_COVID Destination: Draft Checks]
C --> D[End]
Tips¶
-
Review before activation: With Promote As Draft on, newly promoted checks are saved as Draft, so you can make adjustments before using them.
-
Use tags for tracking: Assign a tag like Promoted_Aug2025 to easily find promoted checks later.
-
Keep field names the same: The system only assigns fields when names match. If a field name differs, it is not mapped, which is another reason to keep Promote As Draft on and review the checks.