8. Data Workspace

The Data workspace focuses on building configs, validating files, converting formats, and checking data readiness.

8.1 Configure Wizard

Use Configure Wizard to generate a draft configuration workbook from CSV files, Excel grids, templates, and Application Profile context. Configure Wizard is the main place to create draft configs. Validation and Convertor consume reviewed configs instead of generating them privately.

Modes:

• CSV -> CSV
• CSV -> Grid
• Grid -> CSV
• Grid -> Grid

Inputs:

• Source CSV or source grid.
• Target CSV or target grid where required.
• Application Profile where using profile-assisted generation.
• Location or context where required.
• Template or previous config where using template-guided setup.

Key buttons:

• Run Layout Detection and Extract Member Mapping
• Apply Mapping
• Generate Draft Config
• Run Config Validation
• Download Effective Config Workbook
• Save Effective Config to Template Library
• Download Current Config

Recommended workflow:

1. Select the conversion mode.
2. Upload source and target files.
3. Choose the target layout source, such as Application Profile Assisted or Template Guided.
4. Select the Application Profile and Location if required.
5. Run layout detection and member mapping extraction.
6. Review dimension mapping, member mapping, and Parent Ignore settings.
7. Apply mapping changes.
8. Generate the draft config.
9. Run config validation.
10. Download the effective config workbook.
11. Save the effective config to the Template Library if it is ready for reuse.

Review the detected layout and mapping before generating the final workbook. The review step is where teams should confirm dimension mapping, member mapping, and any ignored parent behavior.

After the draft config is generated, run config validation and confirm that the effective config is valid before using it in Validation or Convertor.

Typical output workbook sheets include:

• Dimension_Mapping_Used
• Member_Mapping_Rules
• Mapping_Explanation
• Mapping_Review_Items
• Validation_Rules
• Output_Settings
• CB_Generation_Context

Best practices:

• Treat Configure Wizard as the main place to generate draft configs.
• Review generated mappings before using the config in Validation or Convertor.
• Save only reviewed and validated configs to the Template Library.

8.2 Validation

Use Validation to compare source and target files using a configuration workbook.

Inputs:

• Source file.
• Target file.
• Configuration workbook.

Modes:

• Single validation.
• Batch validation.

Key buttons:

• Run File Diagnostics
• Run Validation
• Run Batch Validation
• Save Current Config to Template Library
• Open Run Folder
• Open Result

Recommended workflow:

1. Upload or select the source file.
2. Upload or select the target file.
3. Upload or select the configuration workbook.
4. Review the config summary.
5. Run file diagnostics if you want to check file readability before the main run.
6. Click Run Validation.
7. Review passed, failed, warning, and difference items.
8. Open the result workbook or run folder.
9. Save the config to the Template Library only when it has been reviewed.

Outputs:

• Validation result workbook.
• Difference detail.
• Rule hit summary.
• Run summary.
• Local run history entry.

8.3 Convertor

Use Convertor to transform data from one supported format into another using an effective configuration workbook.

Inputs:

• Source data file.
• Configuration workbook.
• Target template or target grid where required.

Key buttons:

• Run Convertor
• Run Batch Convertor
• Clear Target Grid Before Write
• Run Validation Audit After Convert
• Save Effective Config to Template Library

Recommended workflow:

1. Select the conversion mode.
2. Upload the source data.
3. Upload the configuration workbook.
4. Upload the target template or grid if required.
5. Choose whether to clear the target grid before writing.
6. Choose whether to run a validation audit after conversion.
7. Click Run Convertor.
8. Review the output and audit result.
9. Open the result file or run folder from the module or Run History.

Outputs:

• Converted data file.
• Optional validation audit result.
• Run summary.
• Local run history entry.

Best practices:

• Use a reviewed config from Configure Wizard or the Template Library.
• Run Validation before and after conversion when the project requires evidence.
• Keep target templates under version control or project document control.

8.4 Data Readiness Check

Use Data Readiness Check to review whether data and mappings are ready for migration or delivery.

Inputs:

• Artifact kind.
• Project or application context.
• Config workbook.
• Reviewed mapping where available.

Key buttons:

• Prepare Readiness Check
• Use Reviewed Mapping
• Run Data Readiness Check
• Download Readiness Result
• Download Used Config
• Download Generated Config

Recommended workflow:

1. Select the artifact kind and context.
2. Load or generate the relevant config.
3. Use reviewed mapping if available.
4. Prepare the readiness check.
5. Click Run Data Readiness Check.
6. Review blockers, warnings, and recommended actions.
7. Download the readiness result and used config.

Outputs:

• Data readiness workbook.
• Used or generated config.
• Review queue.
• Run history entry.