Dashboard component/business rule
Is it possible to do a live character count using a text box and label component inside of a business rule that counts characters as they are being typed into a text box component that is used in a dashboard? The contents of this text are written to a relational table but as for the character count, I want to do that live BEFORE I write the contents to a relational table. This is on an 8.4 application.
DM Step Issue with Exporting Data with View Filters
Hi team, I'm trying to export data using a Data Management step with view filters. When I specify the view as V#Periodic,V#YTD, only V#Periodic data records is being extracted. If I reverse the order to V#YTD,V#Periodic, then only V#YTD data records get extracted. Has anyone faced this issue or knows how to correctly extract data with View dimension filters? Thanks in advance! 🙂
Meta Data UD2 DIM
We have some group of base customers under different parents with text property, and we are planning to block input to those customers in all the input forms if we use dimension property Allow input 'false' then it will block input but after that update during close FPA team should do adjustments for those Customers. Can we do it with irrespective of that dimension property false update. Is there any option that without updating input forms (CUBE VIEWS) with customer (UD2) parameter or with the help of business rule can we override that dimension property Allow input 'True' by running DM Step for certain customers when we give them in DM JOB and revert again to false after inputs through DM step. Please suggest your solutions.
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?
XF Dimensions Template - Update properties by scenario type
In the metadata XML file, if there are multiple values by scenario type, it splits into two rows and there is no easy way to generate two rows from the XF Dimension template. Is there any way to update member properties varying by scenario type via the upload template? I have to manually update, copy, and paste hundreds of times in order to have that property updated for the accounts. Using the standard metadata builder template, the other properties are getting overridden.
Zero cells count
Hi, I wanted to ask about the OneStream guidelines for an acceptable proportion of zero cells. I remember reading something a few years back about a suggested maximum proportion, but I can't find that info now. I know it's important to minimize zero cells and that there are ways to do this, like using the RemoveZero command in formulas. I also get that the proportion of zero cells is just one part of the overall system performance. Could you share the specific proportion of zero cells to total cells that would typically trigger further investigation? Also, what threshold would indicate that I'm in the clear? I have one client with an existing implementation where zero cells make up about 20% of the total data cell count at the total entity level for Actual. Is that a reasonable proportion? Thanks
Lock Out Sold Entities, Keep Their Impact!
Managing Sold Entities Without Losing Consolidation Results. Hi Community, We’re looking to hear how others handle this in OneStream: When an entity is sold in a specific period (e.g., 2025M5), the requirement is to: ✅ Retain its posted journal values in group consolidation ❌ Prevent any further use of the entity (journals, data loads, forms) The challenge we've encountered is that setting In Use = False — even after journals are posted and consolidation has been run — can cause OneStream to drop that entity’s data from the group during future reconsolidation. This results in the loss of valid P&L impact from the sold entity. Our workaround: Keep In Use = True for the sold period Use workflow locks and security restrictions to block future changes Only set In Use = False once everything is finalized and locked 💡 Feature Suggestion: It would be incredibly useful to have a system property or override flag that allows us to: Set In Use = False to fully disable the entity in the workflow Still retains its consolidated values during reconsolidation How are you managing this today? Your thoughts! Thanks,
