Which type of data source should be created when bringing data in from another OneStream scenario during the Import step?

Which type of data source should be created when bringing data in from another OneStream scenario during the Import step?

• A. Fixed File
• B. Delimited File
• C. A connector
• D. A data management export sequence

Answer: (D)

The data source should be a data management export sequence. This is the built-in mechanism in OneStream for moving data between scenarios or environments. It captures the data values along with the necessary metadata (dimensions, members, periods, versions, etc.) in a OneStream-friendly export that the Import step can read directly, ensuring proper alignment with the target scenario’s structure. Using an export sequence preserves consistency and reduces the need for manual mapping that would be required if you tried to use a plain file. Fixed or delimited files are file-based imports and require separate parsing and mapping, which can be error-prone and may miss metadata. A connector is meant for live integration with external systems, not for transferring data between OneStream scenarios.

The data source should be a data management export sequence. This is the built-in mechanism in OneStream for moving data between scenarios or environments. It captures the data values along with the necessary metadata (dimensions, members, periods, versions, etc.) in a OneStream-friendly export that the Import step can read directly, ensuring proper alignment with the target scenario’s structure. Using an export sequence preserves consistency and reduces the need for manual mapping that would be required if you tried to use a plain file.

Fixed or delimited files are file-based imports and require separate parsing and mapping, which can be error-prone and may miss metadata. A connector is meant for live integration with external systems, not for transferring data between OneStream scenarios.