Upgrade from 9.1 to 9.2
Hi, I would like to know if any major changes need to be carried over from 9.1 to 9.2 version upgrade. As we had some changes performed when we moved from 8.5.1 version to 9.1.0: Winscp to SSH.net Marketplace solutions to be upgraded to latest versions also Navigation center replaced applications reports, security audit reports. so, we had to remove the existing AR, SAR solutions. We had .vb in the extension wherever the xfbr has been referenced that extensions were no longer supported in 9 version. Thanks in Advance!
Complex Expression in Transformation Rule - How to exit rule?
So we have a UD2 mapping set up in the List section. What I want is to be able to set up a Complex Expression in the UD2 Composite section so that for certain accounts it does nothing and so moves on to the List section, but for everything else we have a hard coded UD2 (e.g. None). I have no problem with setting the criteria in the Complex Expression, but I don't know if it is even possible to write some code that forces it to skip on out and look at the List mappings? I realise this is maybe a bit back to front compared to how the Composite mappings work, but we have a very tight list of accounts where we need to do the List UD2 mapping, and everything else (which can be any other account) should just go to None.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
Can 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?
