Speed up procedure development with virtual cubes “on the fly”

Helmut Heimann
Employee, Community Captain




at the moment, every time you realise that you need an additional virtual cube, you have to exit edit mode, switch to options, create a new virtual cube, save it, save the procedure, switch back to edit steps mode. And only then you can define the new data flow.
It would be much better if a new virtual cube could be defined directly from editing the steps.
- determine necessity
- "Create virtual cube", save that
- the virtual cube is directly available
- go on with the flow(s)
This would speed up the development process significantly.
Thanks,
Helmut
Tagged:
16