Promote Overview
Promote is a core operation in Qualytics that allows you to copy and reuse data quality assets across containers and datastores. Instead of manually recreating quality checks, computed fields, computed tables, or computed files in each environment, you can promote them from a source to a destination — preserving definitions and ensuring consistency across your data quality ecosystem.
Why Promote Matters
As your data quality program scales, you often need the same rules, transformations, and computed assets across multiple tables, databases, or environments. Manually duplicating these assets is error-prone and time-consuming. Promote solves this by providing a systematic way to:
- Standardize quality rules: Apply proven quality checks from a reference table to other tables with similar structures, ensuring consistent data quality standards across your organization.
- Replicate across environments: Move quality checks and computed assets from development to staging to production without manual recreation.
- Maintain consistency: When you update a quality check or computed field at the source, you can re-promote it to update the destination — the platform tracks each previous promotion and updates the correct entity.
- Scale computed logic: Reuse computed table and computed file definitions across datastores, avoiding redundant work when the same transformation applies to multiple sources.
What Can Be Promoted
Qualytics supports four types of promote operations, each designed for a specific asset type:
| Asset | Scope | Description |
|---|---|---|
| Quality Checks | Container → Container | Copy quality check rules from one table to another, across the same or different datastores. |
| Computed Fields | Container → Container | Copy computed field definitions from one table to another, across the same or different datastores. |
| Computed Tables | Datastore → Datastore | Copy computed table containers from one JDBC datastore to another. |
| Computed Files | Datastore → Datastore | Copy computed file containers from one DFS datastore to another, with explicit file pattern mapping. |
Key Concepts
- Entity matching is how Promote decides whether to update an existing destination entity or create a new one. The platform first looks up the destination produced by any previous promotion; if none is found, it falls back to semantic matching (by name, or by definition overlap for quality checks). This keeps re-promotion safe — the same source always lands on the same destination, even after edits or renames.
- Per-entity results are recorded for every promotion (created, updated, skipped, or failed) so you know exactly what happened to each entity.
- Async execution means the operation runs in the background — you can monitor its progress from the Activity page.
Deep Dive
-
Getting Started
Learn how promote works, its role in data quality management, practical scenarios, and best practices.
-
Promote Types
Detailed comparison of all four promote types, their scope, parameters, and behaviors.
-
Entity Matching
How the platform decides whether to update an existing destination entity or create a new one — including the two-phase matching strategy.
-
Permissions
User roles and team permissions required to promote — including the dual check on source and destination.
-
Use Cases
Concrete data engineering scenarios — tenant onboarding, environment rollouts, warehouse migrations, schema versioning, and more.
Managing Promotions
-
Promote Quality Checks
Copy quality check rules from one container to another with optional draft mode.
-
Promote Computed Fields
Copy computed field definitions from one container to another.
-
Promote Computed Tables
Copy computed table containers from one JDBC datastore to another.
-
Promote Computed Files
Copy computed file containers from one DFS datastore to another with file pattern mapping.
-
View Promotion Results
Monitor promotion progress and review per-entity results from the Activity page.