Transform Plans
Transform Plans
Section titled “Transform Plans”Overview
Section titled “Overview”A transform plan explains how source fields become governed output fields. It is the review step between raw data and reusable analytics.
How it works
Section titled “How it works”Each target field has a display name, type, mapping rule, optional unit, and optional constraints. Rokks can suggest a plan from sample data, but the user remains responsible for confirming the business meaning. Once loaded, downstream pages read the resulting catalog metadata rather than the raw plan.
Step-by-step
Section titled “Step-by-step”- Open a file area or source that has sampled data.
- Review every proposed target field.
- Rename fields to business-friendly labels.
- Confirm date, number, boolean, enum, and text types.
- Set units where measures need interpretation.
- Mark key fields when they identify records.
- Save or run the load.
Common mistakes
Section titled “Common mistakes”Do not accept vague names such as Column 1 or value when the field has a business meaning. Good names improve dashboards and assistant suggestions.
Do not use a text type for values that need sorting, aggregation, time filtering, or thresholds.