What's new in Customer Journeys?

Connect and learn more! ×
Opinions on Employee Hierarchy in Hybrid Cube? — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Opinions on Employee Hierarchy in Hybrid Cube?

Received Response

I'm just curious on this communities opinions on best practice of Employee hierarchies for Hybrid.

As we know, you can only have 50 members per parent in a Dynamic Calc hierarchy. So in an Employee dimension, it is quite easy to have 1000+ members and it updates fairly frequently.

Is it best to leave it a stored/nevershare? Or is it better to create a ton of layers: Example EM_1000, EM_1100 (child of 1000), EM_1150 (child of EM_1100), then EM_1151 - 1159 under EM_1100. And have it all be dynamic?

I know its a science / art to tune hybrid, and there are lots of factors that make it hard to make absolute rules. But curious thoughts on the above?

Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!