Almost after 4 years, someone found a bug yesterday for the delete operation.
This proves that either the utility is not used by anyone, or no one tried to do something like this so far. π
A friend of mine contacted me to update on an issue he is facing when he is using the delete operation in Essbase member operation utility.
When he ran the utility, he got a message similar to the one below.

It didn’t mention anything about delete, and the member is still present in the outline.
My bad, I never deleted the member, only the message was there π
This update fixes the issue, and below is the message that you’ll see when you delete a level 0 member.

Here is the outline after the delete operation.

You can download the latest version here.
Hello Celvin,
Does it apply any logic on Level 0 Member Deletions?
For instance, if it is the only child and the parent is a Dynamic Calc, does it set the parent to Store or Never Share?
Regards, Kevin
It doesnβt apply any logic now. If it is the only child and the parent is dynamic that is going to error. You need to update the outline first and make the parent stored or never share and repeat the delete operation.