OneStream EmployeeHi, 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.
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
OneStream EmployeeCustom 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.
