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? Cheers13Views0likes0CommentsCan we make consolidation process faster?
Hi, Currently we are not using translation (currency conversion) and I was wondering if we can skip translation process while consolidating or can consolidate only specific accounts (if it allows) to make the process faster? We have a reporting application with huge set of data and need to refresh the data hourly followed by consolidation which is time consuming process. I am using data management out of the box step for consolidation with C#Aggregated. Can I use any other approach to make it faster?55Views1like3CommentsFX Rates by Subsidiary
Hello ONECommunity, We use NetSuite as our ERP system, and we have different FX rates by subsidiaries that apply to the transactions that occur within those subsidiaries. This means that for AverageRate we can have two EUR->USD FX rates within NetSuite. One FX rate for each of the two subsidiaries. When we pull those transactions for our income statement accounts into OneStream to load our YTD Actual scenario, we are seeing some FX variances because OneStream can only apply one EUR->USD FX rate that is stored within the cube's applied FX rate type. How have others solved this issue? Is there a way to apply multiple EUR->USD FX rates within OneStream we are not seeing or is this whole process uncommon and we need some changes to our ERP? Thanks!Solved33Views0likes2CommentsSetDataCell on AdjInput & OwnPreAdj
Hi All - I have a question on the SetDataCell Does the below work? I am trying to write 1 to an account. api.Data.SetDataCell("S#UltOwnShipConsolTracker:V#YTD:A#DirectOwnership:F#None:O#AdjInput:I#None:U1#None:U2#None:U3#None:U4#None:U5#None:U6#None:U7#None:U8#None", 1, False) My Origin is AdjInput & Consol is OwnerPreAdj Thanks Krishna13Views0likes1CommentCube view no input cell based on parameter selection
In the cube view, I have the customer selection on the dropdown list. When NoCustomer is selected, they want to see data that is loaded on Import. But they want to block the input for NoCustomer on Forms. is there an easy way to achieve this? Like if NoCustomer, read only?34Views0likes4CommentsCube | 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.Solved289Views1like3CommentsForce Consolidation Error
Hi Team, Based on Business requirement we have created Stored Calc for Account(A#KPI_GSS_OP_IN_AFT_TAX_ROIC_WIP). But while running the Force Consolidation Step at Parent entity level getting the below error. and consolidation working fine at entity base level and data is sending from source to Destination. Can you please help us on the below issue.16Views0likes0CommentsManagement vs Stat reporting - best practice approach?
Hello, We want to review both our Management and Stat reporting on a monthly basis. The 2 approaches we are considering using are: employ an Audit / Nature UD to build the separate views by adjustments layered over the local GAAP import. or use a separate Scenario for each view with the Local GAAP data being fed into each scenario. One of the main differences between the two views would be pre-acquisition TBs for newly acquired companies being included in the management view for comparative purposes. Would be Interested to hear anyone's feedback or suggestions - thanks!44Views0likes1CommentStored Calc Issue
Hi Team, I am trying to build a Stored calc. My account type is "Revenue" & Formula type is "Formula Pass 11". Here, if i give full combination (All Dimensions) data is sending from Source to designation. and one more thing if i give any variables Data is not sending from source to Destination. can you please help us how to make the calc as dynamic since i am giving all combinations.18Views0likes0CommentsConsolidation percentages bulk load
Hi. I have a lot of changes to consolidation percentages (example : the consolidation % changed in 2024M9 to 60%) to various entities with a time stamp (i.e. history already has default was 100%, then 2023M1 it changed to 80%). However, I cannot just slot the changes into an xml file and load it otherwise it will wipe out the history of the consolidation percentages for those entities and the only info remaining will be the latest change loaded (2024M9 at 60%). Is there a better way to do it than to extract all the ownership information and manually add a new line per entity in the xml extract.26Views0likes1Comment