Cube | Data Access | Data Cell Access Security/Slice Security by U1#Geography
Data Management Access Security Please share your expertise to set up a Cube's Data Cell Access Security / Slice Security to limit data read access as outlined below: Dimension: U1# - Geography Total_Geography = Child 1 + Child 2 = Total / Top North_America = Child 1 / NA International = Child 2 / Int'l Slice Security: Access Level - Read Data by Geography - in a CV and a QV Total_Geo_Data = Read Total data | Read NA data and Read Intl data NA_Data = Read NA data | no data access = International and Total Intl_Data = Read Int'l data | no data access = North America and Total TY for your practical advice - SMEs.
QuickTips: Materiality in the ESG Reporting and Planning Solution
This QuickTips video explores ESG in OneStream, focusing on Materiality in Frameworks. Learn how to designate a KPI as Material or Not Material, sort your KPIs by Materiality, and filter Frameworks to only show relevant KPIs based on Materiality. This video uses ESG version SV100.Supplied Parameters in Workspaces
Hello, I have a button which is fed from a List Box seen below Upon clicking this button, I would like Users to navigate to another Dashboard where the label component and cube view open with this button selection. Are supplied parameters the way to accomplish this? If so, what are the correct configurations to achieve this. Thanks for your help!Using OneStream to Track Inflation and Related Metrics
Hi everyone, I’m interested in learning how other organizations are leveraging OneStream to track inflation and other account-related metrics. Currently, our approach involves using the Account dimension to explicitly separate inflation impacts for specific expense categories. For example: FOOD_BEV – Food & Beverage Expense INFL_FOOD_BEV – Inflation related to Food & Beverage Expense These inflation rates are externally calculated and loaded via XFD uploads. To support different reporting views, we load the data into three separate accounts: _PER – Monthly _QTR – Quarterly _ANN – Annual We also use a view dynamic account without a suffix, which adjusts based on the selected view. Exploring Alternative Approaches I’m considering whether using a User Defined (UD) dimension might offer more flexibility. For instance: Keep the account as FOOD_BEV Use the UD to switch between metrics like: "Dollars" (actuals/estimate) "Inflation" (loaded via XFD) "Per Guest" (dynamically calculated) "Pricing" (potentially another loaded or calculated metric) This method could streamline the structure and allow for more dynamic reporting, especially if inflation rates are only loaded monthly and calculated for QTD/YTD using weighted averages. Open to Ideas I’d love to hear how others are handling similar use cases. Are you using UD dimensions for this type of analysis? Are there better ways to structure inflation tracking in OneStream? Thanks in advance for sharing your insights! — Jeremy Morgan
Confirmation Rules - Time Frequency
Hi there, We've developed rules that works properly in actuals with monthly frequency. Is there a way to use the same rules in other frequencies? I tried to link them to a budget scenario with yearly tracking frequency (Scenario property), but they are applied at the end of the year (for instance 2022) instead of each month. This behavior is kept even after changing to Monthly frequency, or "Member Filter" using "T#|WFYear|.Base". Is there a filter on the time from the WF itself? Ideally, we'd like to keep the actuals conf rules as they are. Thank you for the help. Regards
Best practices for handling overlays with varying dimensionality in OneStream
We are designing a planning solution where overlays will be used across accounts with very different levels of dimensionality. For example: Some accounts have minimal dimensionality (straightforward base members for input). Others require navigating through multiple UDs before reaching the base intersection. Ideally, I’d like users to be able to choose their drill-down path until they reach the correct base intersection for data entry. Has anyone implemented a design pattern or approach that balances these differences effectively?
Combo box cell type not working in Excel
I am working on in OneStream V9. I have a workspace cube view with a combo-box cell type. The cube view works fine in the application, but when I open the same cube view using the Excel add-in the combo-box drop down is not active. Any ideas on what I should check? Thanks.
