Why would you cherry pick department members in Planning webforms? Can't you drive that selection using functions available?
Why not use the Delete Descendants/Delete IDescendants/Delete Level0 in Operation?
Create a load file of the format
Department,Engineering Department,Delete Descendants
This will delete all members under Engineering Department, then you can load members. (You cannot refer members which are used in webform)
Thank Celvin for your reply.
You are right. Leaf level Departments are not used in web-forms and most of them are in Page section. But how about the deletion of approval status as per documentation? Using the approach suggested if we are in middle of budget / forecast cycle and if any member is moved between/across parents or is deleted, what would be the potential impact to change statuses (approval process) and/or planning unit hierarchy?
1 person found this helpful
If you are deleting member which are used in your planning unit hierarchies, then yes those will be removed.
I think if you delete a member (no matter which method you use) those are going to be deleted. Issue that you'll have to worry about is the movement. There is an option to load planning units using outline load, or you can use LCM export the planning units and then import them back once the movement is done.