Which option is NOT a pre-import task according to the list of four tasks?

Which option is NOT a pre-import task according to the list of four tasks?

• A. Build a Data Source in OneStream
• B. Build Data Record Tables
• C. Build Transformation Rule Groups for each enabled Dimension and assign to a Transformation Rule Profile
• D. Assign Data Sources and Transformation Rules to an Import Workflow Profile

Answer: (B)

In a data load workflow, pre-import tasks are about setting up the path the data will take before it gets loaded: where it comes from, how it should be transformed, and how the load is orchestrated. Creating a Data Source establishes the source connection, which is essential before any data can be imported. Building Transformation Rule Groups for each enabled Dimension and assigning them to a Transformation Rule Profile defines how incoming data is mapped and transformed per dimension. Assigning those Data Sources and Transformation Rules to an Import Workflow Profile ties the sources and rules together so the import runs smoothly in an automated process. Building Data Record Tables, however, deals with the structure that holds the data records themselves. This is more about modeling and storage design than configuring the import path, so it isn’t considered a pre-import task. It’s typically done as part of data model design or after the import planning steps, not as part of preparing the import workflow.

In a data load workflow, pre-import tasks are about setting up the path the data will take before it gets loaded: where it comes from, how it should be transformed, and how the load is orchestrated. Creating a Data Source establishes the source connection, which is essential before any data can be imported. Building Transformation Rule Groups for each enabled Dimension and assigning them to a Transformation Rule Profile defines how incoming data is mapped and transformed per dimension. Assigning those Data Sources and Transformation Rules to an Import Workflow Profile ties the sources and rules together so the import runs smoothly in an automated process.

Building Data Record Tables, however, deals with the structure that holds the data records themselves. This is more about modeling and storage design than configuring the import path, so it isn’t considered a pre-import task. It’s typically done as part of data model design or after the import planning steps, not as part of preparing the import workflow.