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
Composite transformation rule with Scenario
I'm trying to do a Composite Rule to Bypass an account if it's part of a specific Scenario? Can you use Scenario as part of an Account Composite Rule? This is my statement "A#[525300]:S#[Budget_Dis...
If your scenario dimension at the data source level is defined from "Global Data Key Scenario" or "Current Data Key Scenario" (the latter is most typical), then it likely will not work in a composite map rule. If instead the scenario is a column or field in the data source, then that composite should work. I would first check how scenario is defined at the data source level.
If scenario is a field in the data source then an alternative to a composite rule is you can concatenate Account_Scenario in your account dimension. Then via mask or 1:1 mappings, you can handle account mappings.
Hey Marcus - how did you make this work? Did you feed the scenario into an attribute field? Across the board, I am using Current Data Key Scenario for my scenario in the data source and can't find a way to leverage the dimension in my mapping.
Looking at this again, the Composite rule works when the Scenario dimension has a Static Value assigned on the Data Source. If the Data Source has 'Current DataKey Scenario'.