Operational Planning Built for Finance Guided Growth

It delivers spreadsheet-like flexibility within OneStream’s unified platform, ensuring governance, scalability, and no-code configuration for business-owned modeling.

Yes. The register is not created when the solution is deployed. It is dynamically defined during setup, allowing flexible column definitions and data types tailored to each model. This allows for higher flexibility and easier mapping of external sources into the register table. There are no pre-defined fields that data needs to map to. The register definition can be modified at any time.

No, the solution is workflow agnostic. The register is not linked to a workflow view for planning and calculations, allowing for higher flexibility and customization of the security model in the planning process. However, data must be processed through a workflow import step to load it into the cube.

Formula creation is UI-driven, using a graphical interface or text input, supporting complex logic without coding, with access to register fields, global drivers, cube drivers, lookup drivers, and prebuilt functions (such as if-then statements and nested logic). The engine supports nested formulas and allows embedding formulas within one another; all managed through the user interface. 

The solution supports global, cube, and lookup drivers, with no need for custom code (XFBR rules). A simplified user interface provides no-code framework for driver development. It allows for variable substitution and multi-dimensional lookups.

No, Line Item Modeling does not support XFBR rules for formulas or calculations. XFBR rules have been removed, and all driver retrieval and formula creation are now handled through a user interface rather than code-based XFBR logic. The code is automatically generated in the backend.

The solution offers granular, role-based security at column, row, and member levels, supporting complex access requirements, including restricting admin access to sensitive columns. Users must be assigned to security groups within the solution to perform actions, even if they are OneStream admins.

Admins must be assigned to the relevant security groups within the solution to have full access. This includes Actions, column visibility, and security assigned to the Entity dimension, UD member definitions, and control lists.

Yes, multiple instances can coexist. Each instance runs independently in its own workspace and schema, allowing you to deploy and manage separate planning models side by side (e.g., workforce, capital, cash, revenue) without interference.

Yes, it requires a minimum platform version of 9.0. It is based on a rearchitected calculation engine that leverages version 9 capabilities and includes new version 9 components such as dynamic grids, which enable us to source data from multiple tables into the register and allows interactive data management.

The solution supports seamless upgrades via a new instance management interface by separating customizations and leveraging configuration files, enabling quick iteration and migration between environments without impacting active plans.

You can set up the solution using either a three-step guided setup wizard or by importing a pre-built configuration file. The setup wizard allows you to define your register (data structure), import data, assign data types, set up member definitions, and apply security.

Dynamic grid is an assembly-driven component in version 9 that allows code to source data from multiple tables into the register, enabling users to interact with and save data back efficiently. It replaces the previous SQL table editor for editing table data and supports high volume data sets through paging.

Transition is handled by exporting the solution metadata as a configuration file (JSON), which includes register definitions, security, drivers, accounts, and formulas, but does not include register data or calculated plan data. Data transition (register data and calculated plan data) is not currently supported due to storage and volume considerations, but it is recognized as a potential future enhancement.

Data can be bulk imported via CSV or connector, and validations ensure data matches register definitions before being saved. A custom stage table has been implemented to execute validation logic.