Hybrid Scenario Issue: Copying Single Period Without Affecting Prior Months
Hello everyone, I’m encountering an issue with Hybrid Scenarios: I’m trying to copy data for a single period only. While I’ve successfully managed to copy Local data for that specific period by updating calc status, the results become inconsistent from Translated up to Top. To align the data from Translated through to Top in the target scenario, I currently need to run a Force Consolidate. However, doing so also brings in data from previous months, which is not desired. Has anyone faced a similar issue or found a way to restrict the consolidation to a single period without impacting prior periods? Thanks in advance,
Consolidate / Aggregate Averages
Good morning all, i've been asked to add some customer satisfaction values to our reports and its just a score out of 5, this works fine for base entities but I really need to parents to be an average of the base Entites that have a value. Is there a way t achieve this? appreciate your time. Tad
Issue Referencing Parent Entity in an Stored Account Member formula
Hi, We have a few accounts that contain stored formulas. These accounts contain formulas that reference another Account and Parent entity and it stores the result at a Base Entity. Below formula is for an account that has a formula pass 4. We are storing the result in "BaseEntity" and calculate Account1 by looking at OPEX at a Parent Entity. Obviously, since it is referencing a Parent Entity we have to run our consolidations twice in order to get the result. Is there a way to sum up the Base entities of Parent1 and reference that value in a formula or is there a way to run a consolidation within the formula for just that Parent Entity? In other CPM/EPM products I've worked with in the past you can right rules where you run an aggregation on the Entity and then run your calculation. In OneStream I cannot seem to find a way to do this. If api.Pov.Entity.Name = "BaseEntity" Then api.Data.ClearCalculatedData("A#Account1",True,False,False,True) api.Data.Calculate("A#Account1 = A#OPEX:E#Parent1:C#USD",True) End If Any help or assistance would be appreciated. Thanks Johnpossibility of UD1 parent-member consolidation by time
Dears, I need move one base member under another parent in UD1 dimensions, the problem is that member should be consolidated till specific time period and then should be consolidated under another parent. There is no option like "percent consolidation" with time frame on UD1 dimensions. Could anyone have any solution for described problem? Before: U1#A(parent) U1#A001(base) consolidated till proper month in 2026 U1#A002(base) After: U1#B(parent) U1#A001(base) consolidated after proper month in 2026 U1#B001(base)Same Scenario Across Two Cubes vs Separate Scenarios — Pros & Cons?
Hello everyone, I’m looking for feedback on the pros and cons of using a single Actual scenario across two cubes (e.g., Consolidation and FP&A) versus defining separate scenarios for each cube. For example: Option 1 (shared): Consolidation Cube : Actual (Scenario Type = Actual) FP&A Cube : Actual (Scenario Type = Actual) Option 2 (separate): Consolidation Cube : Actual (Scenario Type = Actual) FP&A Cube : Monthly (Scenario Type = Control) From your experience, how do these approaches compare in terms of data governance, maintenance, performance, flexibility for planning/reporting, and potential risks (e.g., unintended impacts between cubes)? Any best practices or lessons learned would be greatly appreciated. Thanks in advance!
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!
