Skip to main content
K
kmd
June 27, 2023
Solved

Clearing data for a very specific intersection / Data Unit

  • June 27, 2023
  • 3 replies
  • 2 views

Hi all,

Trying to delete an unnecessary member from the metadata but it won't delete due to 'existing' data.  There isn't actually a value where it says a value exists but OS believes there is data there in currencies that are non-local.

I've tried the DM Clear Data job but it only seems to see the Cube, Entity, Time periods and Scenario.  It appears to ignore any other dimensions specifications I include in any of those filters (i.e. additional UD dimension specifics).  Which makes it too broad for our requirements.  Tried to test this and even though the DM job succeeded for that cube/entity/scenario/time period, it STILL thinks there's data there and won't allow the deletion of the member.

Hoping someone out there has run into a similar situation and has some suggestions to offer on how to truly clear a member completely so it can be removed from the metadata.  Thanks

Best answer by JackLacava

If you have a problem, if no one else can help, and if you can find them, maybe you can use... finance Api rules!

 

api.Data.ClearCalculatedData(True, True, True, True, "A#MyAccountParent.Base", "F#MyFlowParent.Base") '... other filters if necessary
api.Data.SetDataCell("A#MyAccount:F#MyFlow", 0,True) ' other members as necessary, if not specified will fall back to None

 

Drop that in a Custom Calculate, execute it with the related Data Management step, and you should be able to clear the specific intersections you need.

3 replies

J
JackLacavaAnswer
June 27, 2023

If you have a problem, if no one else can help, and if you can find them, maybe you can use... finance Api rules!

 

api.Data.ClearCalculatedData(True, True, True, True, "A#MyAccountParent.Base", "F#MyFlowParent.Base") '... other filters if necessary
api.Data.SetDataCell("A#MyAccount:F#MyFlow", 0,True) ' other members as necessary, if not specified will fall back to None

 

Drop that in a Custom Calculate, execute it with the related Data Management step, and you should be able to clear the specific intersections you need.

K
kmdAuthor
June 27, 2023

Thank you so much for this - it will be very handy for us as we have to clear > 2000 members.  Very much appreciated!!

M
MikeG
June 27, 2023

There could be translated data at a non-local currency.  Go to System > Database tab > then Data Records.  Put in the Time in the format T#2023 (full year) and in this view Value1, Value2, Value3 represent the Months M1, M2, M3.  This will at least identify the intersection of data where the data exists.

If it is only translated data, and the source data in Local has been deleted, then you just need to run a Force Consolidate to clear the translated data.  

Lastly, I have a BR that will do a targeted clear of a data cell.  If you paste a reply here of the intersection you are trying to clear (Entity, Account, Origin, etc) I'll mock it up and post the code here for you.

Hope that helps.

K
kmdAuthor
June 27, 2023

Thank you so much for this.  You are exactly right.  After I posted the question, I wondered about the same thing and went ahead with a force consol and voila - it worked.  Thank you again

M
MikeG
June 27, 2023

Keep that code handy that JackLacava posted in this thread.  That is solid.  On your OS journey, you'll need to know how to do what Jack pasted here at some point.

Glad that worked for you.

Terms & ConditionsAccessibility statement