A trick I have used in the past is to create a dummy parent entity "TO_BE_REMOVED" and move the orphans all under that one parent. Then you can run a clear using a DM sequence focusing on E#TO_BE_REMOVED.Base". Once data is cleared you can re-orphan them and delete them with the UMA tool on Open Place or a delete utility.
OneStream EmployeeA trick I have used in the past is to create a dummy parent entity "TO_BE_REMOVED" and move the orphans all under that one parent. Then you can run a clear using a DM sequence focusing on E#TO_BE_REMOVED.Base". Once data is cleared you can re-orphan them and delete them with the UMA tool on Open Place or a delete utility.
This trick didn't work in our case Because Share member has data which is Custom calculated. This approach would definitely work in case of Dynamic data.
