🧭✨Future Applications (NEW)
✨ NEW TABLE - December 2025
🛠️ Partner API Alignment Migration
🧭 This table represents the post-migration state for
applications.1️⃣ Migrate to this table by April 2026
2️⃣ Between April 2026 and July 2026, remove FUTURE__ prefix
Contains application data filtered for specific operators and their parent operators. This model provides a focused view of applications relevant to particular operator relationships, including application metadata and lifecycle information.
SQL: FUTURE__applications
Schema
| Column Name | Data Type | Description |
|---|---|---|
| Primary ID | ||
| id | INTEGER | Primary key |
| Other IDs | ||
| operator_id | INTEGER | Unique identifier for the operator associated with the application |
| parent_operator_id | INTEGER | Identifier for the parent operator in hierarchical operator relationships |
| Timestamps | ||
| created_at | TIMESTAMP_NTZ | Timestamp when the application record was originally created |
| deleted_at | TIMESTAMP_NTZ | Timestamp when the application was marked as deleted, null if still active |
| operator_deleted_at | TIMESTAMP_NTZ | Timestamp when the associated operator was deleted, null if operator is still active |
| Attributes | ||
| application_name | VARCHAR | Display name or title of the application |
Changes from Last Version
Added columns (1):
- operator_deleted_at
Removed columns (0):
- no columns were removed
Renamed columns (1):
- application_id → id
Data inclusion criteria
This table works with operator_id or parent_operator_idmust match the operator's ID.
Data flow
| Upstream tables | Downstream tables |
|---|---|
| --- | --- |
Alignment
applications table
applications tableexclude rows where operator_deleted_at is not null
where operator_deleted_at is nullUpdated about 22 hours ago
