Import, Validate, Load Overview
Every time external data enters a OneStream Cube — whether from an ERP extract, a flat file, or a database connector — it passes through the Import, Validate, Load (IVL) pipeline. IVL is not a standalone tool; it is a sequence of Workflow tasks that the Data Management / Stage Engine orchestrates. This guide introduces the pipeline end-to-end before the subsequent guides dive into each step.
Where IVL Fits in the Workflow
A OneStream Workflow is the governance backbone for every financial process — closing the books, loading actuals, entering budgets, certifying data. A single Workflow Profile ties together an Entity (or set of Entities), a Scenario, a Time period, and a series of tasks the user must complete.
For data loading, the tasks on the Workflow task bar are literally Import → Validate → Load. The Workflow Name property on the profile controls which tasks appear. Setting the Workflow Name to
Import, Validate, Load gives the user all three discrete steps. Other names like Load And Transform or Direct collapse these into fewer steps.The End-to-End Flow
Each step has a distinct purpose:
| Step | What Happens | Key Output |
|---|---|---|
| Import | The user uploads a file or triggers a connector. The Stage Engine parses raw data into a tabular staging format and applies Transformation Rules to map source values to Cube dimension members. | Staged and transformed records |
| Validate | The system checks that every staged record has a valid mapping (Transformation Validation) and that the resulting dimension intersections are legitimate (Intersection Validation). | A pass/fail status with error details |
| Load | Validated records move from the Stage tables into the Cube. The engine loads in parallel by Entity for throughput. | Data available in the Finance Engine |
After all three steps complete successfully, the Workflow advances to the next task — typically Process Cube (which runs consolidation calculations) or Certify.
Status Indicators
Each Workflow task on the task bar uses color to communicate its state:
| Color | Meaning |
|---|---|
| Blue | Not yet started, or in progress |
| Green | Completed successfully |
| Red | Completed with errors that must be resolved |
When Import finishes without errors, it turns green. When Validate finds transformation or intersection errors, it turns red — you must fix the mappings and re-validate before you can proceed to Load. When Load completes, it turns green and the Workflow moves forward.
Workflow Name Options
The Workflow Name property determines which IVL tasks appear on the task bar. Common configurations:
| Workflow Name | Tasks Shown | Use Case |
|---|---|---|
Import, Validate, Load | Import → Validate → Load (three separate steps) | Standard data loading with full control |
Load And Transform | A single combined step | Simpler UX when validation is minimal |
Direct | A single in-memory step (no Stage persistence) | High-performance production loads with stable mappings |
Import, Validate, Load, Certify | Import → Validate → Load → Certify | Data loading with sign-off in one Workflow |
The choice depends on your data complexity and governance requirements. The remaining guides in this series assume the full
Import, Validate, Load configuration unless stated otherwise.Common Gotchas
Before diving into each step, keep these cross-cutting rules in mind:
- Origin Dimension enforcement — The Workflow Engine forces imported data to the Import member of the Origin dimension and the Local member of the Consolidation dimension. You do not control this; it is automatic.
- Reserved characters — The characters
!,?, and|are used internally by Transformation Rules. Never use them in Source or Target member names. - Enforce Global POV — When enabled under Application → Tools → Application Properties, data loading is restricted to the Global POV time range. Users cannot import data outside the enforced period.
- Retransform after rule changes — In a Standard Workflow, always click Retransform after editing Transformation Rules. This re-applies all rules without re-importing the file.
- Intersection errors are second-pass — Transformation errors are checked first. You will not see intersection errors until all transformation errors are resolved.