I had the impression that if an object was locked e.g. an element or cube, any data for that object could not be changed or deleted without unlocking the object. Apparently this is not the case when using the CubeClearData TI function. Is this correct?

I cannot find any mentioning of this in the documentation.

------------------------------
Jesper Poulsen
------------------------------

#PlanningAnalyticswithWatson

Just for clarity, when you say lock I think you mean in the security sense rather than the database sense that an object is locked because it is being edited (for example)?

If so then I agree that CubeClearData should be respecting the lock security status of the cube.

That said I'm not surprised that it doesn't, the functions intent is to clear all the data in the cube and it sounds like that is what it is doing.  I'd not be at all comfortable building a View Zero Out job that relied on the correct locking to be in place for it to function correctly.  Much safer to use VIewZeroOut and then explicitly add what you want to clear.

------------------------------
Steven Rowe
------------------------------

Original Message:
Sent: Mon June 29, 2020 04:07 AM
From: Jesper Poulsen
Subject: CubeClearData function and object lock

I had the impression that if an object was locked e.g. an element or cube, any data for that object could not be changed or deleted without unlocking the object. Apparently this is not the case when using the CubeClearData TI function. Is this correct?

I cannot find any mentioning of this in the documentation.

------------------------------
Jesper Poulsen
------------------------------

#PlanningAnalyticswithWatson

Hi Steven.

Yes, it is locking in the security sense.

And I totally agree on your ViewZeroOut point which I normally follow. But I had a case where I wanted to test if I could use the locking and CubeClearData in  combination and apparently it is not possible.

------------------------------
Jesper Poulsen
------------------------------

Original Message:
Sent: Thu July 09, 2020 04:43 AM
From: Steven Rowe
Subject: CubeClearData function and object lock

Just for clarity, when you say lock I think you mean in the security sense rather than the database sense that an object is locked because it is being edited (for example)?

If so then I agree that CubeClearData should be respecting the lock security status of the cube.

That said I'm not surprised that it doesn't, the functions intent is to clear all the data in the cube and it sounds like that is what it is doing.  I'd not be at all comfortable building a View Zero Out job that relied on the correct locking to be in place for it to function correctly.  Much safer to use VIewZeroOut and then explicitly add what you want to clear.

------------------------------
Steven Rowe

Original Message:
Sent: Mon June 29, 2020 04:07 AM
From: Jesper Poulsen
Subject: CubeClearData function and object lock

I had the impression that if an object was locked e.g. an element or cube, any data for that object could not be changed or deleted without unlocking the object. Apparently this is not the case when using the CubeClearData TI function. Is this correct?

I cannot find any mentioning of this in the documentation.

------------------------------
Jesper Poulsen
------------------------------

#PlanningAnalyticswithWatson

Hi,

######
Apparently this is not the case when using the CubeClearData TI function. Is this correct? ​​
#######

Looks you are correct. 

Because according to documentation: any cells in the cube that are fed with feeders are also cleared
meaning the lock object will be ignored as well. 


​

------------------------------
Veronika Gultom
------------------------------

Original Message:
Sent: Mon June 29, 2020 04:07 AM
From: Jesper Poulsen
Subject: CubeClearData function and object lock

I had the impression that if an object was locked e.g. an element or cube, any data for that object could not be changed or deleted without unlocking the object. Apparently this is not the case when using the CubeClearData TI function. Is this correct?

I cannot find any mentioning of this in the documentation.

------------------------------
Jesper Poulsen
------------------------------

#PlanningAnalyticswithWatson