Refresh of Spreadsheet with the Cube Views and Table View
Hi all, for one customer we need to prepare a an input file template with cube views to deliver correct metadata (dimensions). The Idea is to prepare as much data and metadata from the applicatoion for the user as possible. We were not able to find a solution how to retrieve a list of all entities when the user has access only few out of all. So we switched to the Table view. We created a dashboard containing the spreadsheet with the template that is refreshed at load. The trouble is refresh itself. If I have a blank spreadsheet and add the table view there, the refresh (TV or the whole Sheet) is almost instant. If I have the template with just some Cube Views, it is also very quick (few seconds). But refresh of the same template with added Table View takes almost 2 minutes and it freezes the client and even the Excel if I use the add-in. Would you have any recommendations?
How to move accounts from one hierarchy to another one
Hi, In our application Account hierarchy is Root>GL_Accts>SGL_Accts. The account A is created under "GL_Accts" heirarchy. The business requirement is the account A should move under SGL_Accts hierachy. Can we make change this change? please advise.
How to Add Adjustments with Add Back Category and Free-Form Add Back Name to Actuals in OneStream?
Hi Everyone, I’m working with Actuals data structured like the attached screenshot and want to add adjustments linked to this data. Key points: Adjustments must tie to Actuals by Company, Account, and Month Each adjustment includes: An Add Back Category An Add Back Name, which is free-form text and can vary monthly I want to maintain monthly detail and enable reporting and drill-down by both Add Back Category and Add Back Name My questions: What’s the best approach to model and load adjustments with both a Add Back Category and a free-form Add Back Name in OneStream? Should Add Back Name be a UD member with auto-create, a text attribute, or something else? How to avoid member explosion or reporting complexity given the free-form nature of Add Back Name? How can I ensure adjustments roll up correctly and maintain data integrity? Any recommendations for validation, governance, and reporting for this kind of adjustment detail? Thanks in advance for your insights!
Best way to narrow down where a simple account name is used (ex. AR)
Hello! We named an alternate hierarchy account parent AR and are now trying to find where that account was called/used because we want to remove it without impacting other things (we'll redirect wherever it's referenced to its replacement/new hierarchy). We use Finit's Toolkit/SearchIt (replaced by OS's ownership in more recent releases) but as you can imagine, searching "AR" gets 100s/1000s of matches. Is there a way folks might suggest to narrow down this search? A#AR has helped but I'm afraid we'll still miss areas where the A# isn't referenced in front of the account name. We also tried searching the member ID in SearchIt and that doesn't work. Any suggestions appreciated! Thanks! -Nicole
Dynamic Dimensions/Cube Services
Hello everyone, Trying to create dynamic dimension in v9.0 application, I'm not able to an option to do the same in the create dimension source type dropdown. Only seeing the following Same issue with creating Dynamic Dimension in a Service Factory (see ss below) Also not able to see any Data Binding Type setting on the cube in order to turn the into dynamic cube Does anyone have any idea if I may be missing anything here, or does the dynamic cube/dimensions is something I have to ask OS to enable in my application? Appreciate your time, thank you!Can constraints Slow Things Down in OneStream?
Constraints in OneStream are filters applied to metadata dimensions such as Flow, Accounts, UD1, or specific cash flow lines to narrow the scope of calculations, data retrieval, or Cube View rendering. They’re powerful tools, but when applied too broadly or dynamically, can they degrade performance? Larger evaluation footprint A Flow or Account constraint forces OneStream to check every intersection in that dimension. In dense cubes, this can mean millions of evaluations. 1. Dynamic filters are expensive. Static lists (e.g., A#1000, A#2000, Flow#Operating) resolve quickly. Dynamic logic FilterDim, Boolean conditions, or formula driven sets require runtime computation. Why? 2. Stacked or nested constraints multiply the cost. Does layering constraints across Flows, Accounts, and UDs in OneStream force the system to resolve each filter before executing calculations? 3. Reduced parallelism. When constraints slice across cash flow lines or UD dimensions, the engine can’t fully parallelize tasks. Does more constraint mean fewer threads working freely? Do you agree? Why? Cheers
