Cubes in Essbase vs 1Stream
Happy inflation and food shortages <Not!!>
Quick question. I have over 15 years experience in Essbase and find it confusing that we have multiple 1Stream cubes in one 1Stream application - but they all share the same outline!! I think I understand 1S extensibility.
Is there an article that explains the differences of Essbase vs 1Stream?
I would like to suggest to 1Stream developers to show cube name somewhere when I open a workflow. I don't see a way to tell if that workflow is for which cube!! very confusing.
1) One workflow controls/updates one Toplevel Cube and its descendants. An embedded cubeview can be used to input data in multiple, none related cubes, but these cube's input isn't controlled by the workflow (e.g. out of the box you can't lock it within the workflow).
2) You can always look at a Cell's pov:
to get the cube information
If you like, you can use the name command to add the cube name to a row or column header: |CVCube| but typical we don't like the end users to get confused by cube.
3) No 'Clubs Parent Adj' is using the Golfstream cube and it uses the same cube like Frankfurt, but Houston has its own cube, but it is an extended cube of Golfstream. But all cubes are related to Golfstream.
4) No Parent id just the gender neutral version of father or mother.