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, they can quietly 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—requires runtime computation, which is slower. 2. Stacked or nested constraints multiply the cost. Layering constraints across Flow, Accounts, and UD1 means OneStream must resolve each filter before executing calculations, compounding runtime. 3. Reduced parallelism. When constraints slice across cash flow lines or UD dimensions, the engine can’t fully parallelize tasks. More constraint logic means fewer threads working freely. Do you agree? Why? Cheers
Backward compatibility in client software
Hi Onestream experts, We need to install client software 9.1.0 for accessing Environment 1, which is running on version 9.1 We could not use the client software 9.1.0 for accessing Environment 2, which is running on version 8.4 Why is the client not backward compatible? This is a very normal situation for any customer, to have different environment in different version. How to solve this? Thanks Suresh
Member PropertyID Data Dictionary
Hello OneStream Community, A few days ago a colleague of mine wanted to know the meaning of the various PropertyId constants present in one of the Application Database Audit Tables. I was unable to find any OneStream specific documentation on this PropertyId code and its meaning, so I created a business rule to complete the puzzle and get what we needed for the metadata audit at a very granular level. For any one else experiencing an issue similar like this here is a table of the Member property Id's and their meaning. Dimension | PropertyID | PropertyDescription Entity PropertyID | 100 | Currency Scenario PropertyID | 100 | ScenarioType Account PropertyID | 100 | AccountType Entity PropertyID | 150 | IsConsolidated Entity PropertyID | 200 | IsIC Scenario PropertyID | 200 | InputFrequency Account PropertyID | 200 | FormulaType Flow PropertyID | 200 | FormulaType UDx PropertyID | 200 | FormulaType Scenario PropertyID | 300 | DefaultView Account PropertyID | 300 | AllowInput Flow PropertyID | 300 | AllowInput UDx PropertyID | 300 | AllowInput Scenario PropertyID | 400 | CalculateFromGridsGroup Account PropertyID | 400 | IsConsolidated Flow PropertyID | 400 | IsConsolidated UDx PropertyID | 400 | IsConsolidated Scenario PropertyID | 500 | ManageDataGroup Account PropertyID | 500 | IsIC Flow PropertyID | 500 | SwitchSign UDx PropertyID | 500 | AlternateCurrencyForDisplay Account PropertyID | 600 | UseAltInputCurrencyInFlow Flow PropertyID | 600 | SwitchType Account PropertyID | 700 | PlugAccount UDx PropertyID | 10100 | IsAttributeMember UDx PropertyID | 10200 | AttributeMemberSourceMember UDx PropertyID | 10300 | AttributeMemberExpressionType UDx PropertyID | 10400 | AttributeMemberRelatedDimType1 UDx PropertyID | 10500 | AttributeMemberPropType1 UDx PropertyID | 10600 | AttributeMemberComparisonText1 UDx PropertyID | 10700 | AttributeMemberOperatorType1 Scenario PropertyID | 30100 | InputViewForAdj Account PropertyID | 30100 | InputViewForAdj Scenario PropertyID | 30200 | NoDataZeroViewForAdj Account PropertyID | 30200 | NoDataZeroViewForAdj Scenario PropertyID | 30300 | NoDataZeroViewForNonAdj Account PropertyID | 30300 | NoDataZeroViewForNonAdj Scenario PropertyID | 30400 | ConsolidationView Scenario PropertyID | 30500 | Formula Scenario PropertyID | 40000 | UseInWorkflow Scenario PropertyID | 40100 | WorkflowTrackingFrequency Scenario PropertyID | 40500 | WorkflowNumNoInputTimePeriods Scenario PropertyID | 50100 | UseCubeFxSettings Account PropertyID | 50100 | UsedOnEntityDim Flow PropertyID | 50100 | FlowProcessingType Scenario PropertyID | 50200 | FxRateTypeForRevenueExpense Account PropertyID | 50200 | UsedOnConsDim Flow PropertyID | 50200 | AlternateInputCurrency Entity PropertyID | 300100 | FlowConstraint Account PropertyID | 300100 | FlowConstraint Entity PropertyID | 300200 | ICConstraint Account PropertyID | 300200 | ICConstraint Entity PropertyID | 300400 | UD1Constraint Account PropertyID | 300400 | UD1Constraint Entity PropertyID | 300500 | UD2Constraint Account PropertyID | 300500 | UD2Constraint UDx PropertyID | 300500 | UD2Constraint Entity PropertyID | 300600 | UD3Constraint Account PropertyID | 300600 | UD3Constraint UDx PropertyID | 300600 | UD3Constraint Entity PropertyID | 300700 | UD4Constraint Account PropertyID | 300700 | UD4Constraint UDx PropertyID | 300700 | UD4Constraint Entity PropertyID | 300800 | UD5Constraint Account PropertyID | 300800 | UD5Constraint UDx PropertyID | 300800 | UD5Constraint Entity PropertyID | 300900 | UD6Constraint Account PropertyID | 300900 | UD6Constraint UDx PropertyID | 300900 | UD6Constraint Entity PropertyID | 301000 | UD7Constraint Account PropertyID | 301000 | UD7Constraint UDx PropertyID | 301000 | UD7Constraint Entity PropertyID | 301100 | UD8Constraint Account PropertyID | 301100 | UD8Constraint UDx PropertyID | 301100 | UD8Constraint Account PropertyID | 500100 | WorkflowChannel UDx PropertyID | 500100 | WorkflowChannel Entity PropertyID | 500300 | SiblingConsolidationPass Entity PropertyID | 500500 | AutoTranslationCurrencies Entity PropertyID | 700100 | InUse Account PropertyID | 700100 | InUse Flow PropertyID | 700100 | InUse UDx PropertyID | 700100 | InUse Entity PropertyID | 700200 | AllowAdjustments Account PropertyID | 700200 | Formula Flow PropertyID | 700200 | Formula UDx PropertyID | 700200 | Formula Account PropertyID | 700210 | FormulaForCalcDrillDown Flow PropertyID | 700210 | FormulaForCalcDrillDown UDx PropertyID | 700210 | FormulaForCalcDrillDown Entity PropertyID | 700300 | AllowAdjustmentsFromChildren Account PropertyID | 700300 | AdjustmentType Entity PropertyID | 900100 | Text1 Scenario PropertyID | 900100 | Text1 Account PropertyID | 900100 | Text1 Flow PropertyID | 900100 | Text1 UDx PropertyID | 900100 | Text1 Entity PropertyID | 900200 | Text2 Scenario PropertyID | 900200 | Text2 Account PropertyID | 900200 | Text2 Flow PropertyID | 900200 | Text2 UDx PropertyID | 900200 | Text2 Entity PropertyID | 900300 | Text3 Scenario PropertyID | 900300 | Text3 Account PropertyID | 900300 | Text3 Flow PropertyID | 900300 | Text3 UDx PropertyID | 900300 | Text3 Entity PropertyID | 900400 | Text4 Scenario PropertyID | 900400 | Text4 Account PropertyID | 900400 | Text4 Flow PropertyID | 900400 | Text4 UDx PropertyID | 900400 | Text4 Entity PropertyID | 900500 | Text5 Scenario PropertyID | 900500 | Text5 Account PropertyID | 900500 | Text5 Flow PropertyID | 900500 | Text5 UDx PropertyID | 900500 | Text5 Entity PropertyID | 900600 | Text6 Scenario PropertyID | 900600 | Text6 Account PropertyID | 900600 | Text6 Flow PropertyID | 900600 | Text6 UDx PropertyID | 900600 | Text6 Entity PropertyID | 900700 | Text7 Scenario PropertyID | 900700 | Text7 Account PropertyID | 900700 | Text7 Flow PropertyID | 900700 | Text7 UDx PropertyID | 900700 | Text7 Entity PropertyID | 900800 | Text8 Scenario PropertyID | 900800 | Text8 Account PropertyID | 900800 | Text8 Flow PropertyID | 900800 | Text8 UDx PropertyID | 900800 | Text8
Archive applications
Hi all, How do other customers go about archiving applications? We've been live since 2017 and every year after filing our SEC reporting, we copy the production application and rename it with the year that's being archived. This is helpful as in the past we've move products in segments as well as various other master data changes affecting reporting. The issue is that now we're nearing our storage capacity as the size of our application has grown over the years as we add in more data and features (35GB for the 2018 archive while our current 2021 production app is at 155 GB) and clearly this problem will continue every year. Any suggestions on a more efficient and cost-effective strategy? Thanks!
Pivot Grid Modern Browser Experience allow additional default fields
Our team would like an enhancement to the Web version of the client (Version 9.0.0) as the Modern Browser Experience does not allow us to use the default pivot grid views we created. The default pivot grid views we created work great in the Desktop version, but they do not work for our Browser version because we exceed the number of allowed default fields. This enhancement would allow our users to save time with the ability to use default views, instead of needing to add in the fields manually each time.
Environment Management
Hi All, In your OneStream implementation, how many environments do you have? Dev, UAT and Prod? Or do you also have Pre-Prod environment that is common in ERP systems? Also, in the UAT environment do you also have copy of data so that when testing happens or developers need to test the changes - there is enough sample data to test? Would you consider brininging data from Prod, randomize it and load into UAT env so that UAT env data at all intersections as Prod? Thanks!Database space control policies
Hi! We are trying to control the size increase in our production application. We know the growth comes from: Stage tables that allow users to drill down and back onto source data. Data records Audit tables (they can grow a lots if they are recording continuous changes to rules, data for example) Logs which will impact Framework database growth (task activity and error logs, will vary depending on the detail login set in BR, DM and on the system configuration as well as your retention policy) Load transactional data, which will increate your data units and data records unnececarily, which BIBlend should be used for this type of data load instead of loading it to the finance cube. We have analyzed it and we realized the StageAttributeTable and other stage tables has a significant size. Has ayone performed databse maintenance by deleting data from the stage tables? Is it possible to do that while keeping the cube data intact and workflows completed? Any ideas or best practices regarding database maintenance would be very welcome. Regards, XaviUsing 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
