Forum Discussion

Satish's avatar
Satish
New Contributor II
1 day ago

Custom Consolidation

Hi,

I have a requirement from business that, want to restrict the roll-up in the entity dimension.

for ex: i have Top entity, and all the members underneath are rolling up to Top, but i want to restrict one entity (ex: entity A) not to roll up for particular users which are part of group A.
So, when Group A users retrieve the data at Top entity, he/she should see the total number except restricted entity(entity A) and all other can see the total numbers including entity A at Top.

is there any way to restrict the roll-ups based on security.

Thanks in Advance.
any suggestions please, Appreciate your help.

Thanks
Satish P

Finance

5 Replies

  • MarcusH's avatar
    MarcusH
    Valued Contributor
    4 hours ago

    I agree with Henning​ that an alternative hierarchy is the simplest way to do it. Another scenario I think has too many problems associated with syncing data. I suppose you could write a custom consolidate BR that updates a UD member during consolidation. You have UD members GroupA, OthersGroups and their parent is TotalGroups. During Consolidate, the BR looks for the Entity being consolidated - if it's GroupA, the UD member for the data is switched to GroupA, everything else goes to OthersGroups. Then use Slice Security so that GroupA users only see OthersGroups and everyone else sees TotalGroups. I'm not recommending it; it's a possibility.

  • Kamila's avatar
    Kamila
    Contributor
    7 hours ago

    Hello Satish,

    What came to my mind is just create a new scenario, copy there records from your old scenario. Then in Entity dimension -> Relationship Properties -> scenario type you can change consolidation from 100 to 0. It will just affect this one scenario 

     

  • Henning's avatar
    Henning
    Icon for OneStream Employee rankOneStream Employee
    1 day ago

    Hi, just create an alternate hierarchy in the entity dimension without entity A and give your restricted user only access to this alternate hierarchy. Seems like the easiest option to me.

    • Satish's avatar
      Satish
      New Contributor II
      14 hours ago

      Hi,

      Thanks for your comments.
      We would prefer not to create an alternate hierarchy. Is there any other approach to achieve this?

      I am aware that OneStream provides Custom Consolidation options within the Cube settings, which allow us to control or override parts of the consolidation process.

      If anyone has experience implementing or configuring Custom Consolidation rules, insights or examples would be really helpful.

      Thanks
      Satish P

      • Henning's avatar
        Henning
        Icon for OneStream Employee rankOneStream Employee
        5 hours ago

        Custom consolidation rules are not a good fit for the described purpose. That would bring along added complexity and impacting performance for something that can be solved easily by different means. 

        Another scenario such as the one Kamila suggested is an option too, though the total data volume stored in the app is larger than using an alternate hierarchy. In normal apps that is still perfectly fine though.

        One could also use dynamic cube services (DCS). But again, that is more complex and I want to describe it as "shooting sparrows with a cannon" in the given context.