The OneStream Community is temporarily frozen until June 29th due to the ongoing maintenance. Please read the blog post here to learn more.
Forum Discussion
Solved
Pre-aggregated Origin Members on a Hybrid Scenario
I set up a Hybrid Scenario with a Data Binding Type of "Copy Input Data from Source Scenario." I tried following the example in the Design and Reference Guide (below) for the Origin dimension, where ...
Hi Molly,
Can you use "Share Data from Source Scenario" instead? With the copy selection, you copy data from one scenario to another and then consolidate the new scenario, which then eliminates all IC data (and possibly custom rules) in the new scenario which is why you see data on O#Elimination I assume.
When you use "Share", the data will dynamically be displayed, without eliminating during a consolidation.
Henning
OneStream Employee
OneStream EmployeeHi Molly,
Can you use "Share Data from Source Scenario" instead? With the copy selection, you copy data from one scenario to another and then consolidate the new scenario, which then eliminates all IC data (and possibly custom rules) in the new scenario which is why you see data on O#Elimination I assume.
When you use "Share", the data will dynamically be displayed, without eliminating during a consolidation.
Hi Henning,
What is the best solutions to follow when needing to use Hybrid Scenario design, but the target scenario data needs to be edited?
Share Data from Source Scenario would be the preference due to performance, but its a read only version.
Copy Input Data from Source Scenario (like Molly suggested) is therefore the "obvious" choice here, but it takes quite a while to run a copy as a force calculate needs to be executed instead of a calculate (which would be the preference).