Designing extensibility in OneStream XF always relies on a couple of important things:
The following are all actions that Extensible Dimensions can do:
The following are all actions that Extensible Dimensions can't do:
Please Note: Inherited dimensions can't change an extended Base Member into a Parent and they can not see extended Members in their Dimension.
Below is an example of what kind of questions you should consider asking users on Extensibility:
Please Note: The total amount of questions you can ask your clients is not limited to just these 4. Instead, think of this list as a beginning spot on what kinds of questions you should consider asking.
The main goal of a design session for extensibility is to define the lowest common dimensions and extension points (horizontal/vertical extension points, large and sparse partition points, etc.).
Consultants will go through each Scenario Type and ask users which level each Account Dimension is collected on. The consultants will then go through each Business Unit and ask users if the Unit is different from other Units, and if this Unit can extend Account Level Dimensions. The last topic that consultants will go over are the proposed Models. Consultants will ask users if the model contains large sparse trigger Dimensions, if the company will consolidate large amounts of data, and if the model has Attribute Type Dimensions that will change over time.
Usually, consultants should be prepared to build and demo a skeleton model to show users for validation.