Cube VIEW Security TURBO INTEGRATOR

[mnasra]

I have a TI process creating data into a cube from a view from another cube (Actuals into budget of second cube).
Everything works fine. But my problem, is that the view for the TI is public.
I have users who read it, and save it with different data.
How can I secure these views made only for TI- so no one can see them, use them or delete them, or even try to read them (which gives them memory error anyway).

Thanks

[jim wood]

As far as I know (based on earlier versions) there is no way of securing it. It has to be a public view. You could always assemble the view in the TI process or even assemble it in another process before running the copy. Then kill the view once the load is complete,

Jim.

[mnasra]

Oh- I never thought of assembling the view in the TI process-
THANKS
Micheline

[Steve Vincent]

Jim is (still) right - all TI views must be public, there is no way to hide them. Either name them so they fall at the end of the list of views (zPro_Blah) or as Jim suggested create the subsets and view as part of the TI itself. You can then destroy those objects after the TI has done what it needs to.

[Martin Ryan]

There's an outstanding request from the community to rectify this as IMHO it's a pretty big failing for an industrial tool.

You might want to raise an enhancement request with IBM too. They might eventually pay attention to us.

Martin