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_Dist]" that isn't working.
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.
7 Replies
- T_Kress
OneStream Employee
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.
You are my hero! I was about to go crazy on that! Thank you that was exactly what my issue was, I just had to make it a stored value on my Data Source which is okay for this situation, and it made the composite rule work.
Hi,
Is the account group placed after the scenario group in the transformation profile? See below an example, Scenarios are placed before Account rules in the profile:
Thanks,
Ioana
The order of the dimensions in the Transformation Profile does not control the order in which the dimensions are processed. That is controlled by the Transformation Sequence for the dimension (Application | Cubes | Integration). The Transformation Profile controls the order in which the Transformation Groups are processed within a dimension. If you only have 1 transformation group per dimension, the Transformation Profile has no impact on the processing order. And the Scenario dimension does not have a Transformation Sequence as the the Integration tab is split by Scenario Type.
You can use the Scenario as part of a composite rule - it works for me in V7.4.
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'.
