ListDeletedObjects returns empty vector for real entity path

[surak8]

When preparing to obliteraate files, ListDeletedObjects works for "$" or "$/" but any real path (i.e. "$/DotNet/DealViewer") returns an empty vector.

My desire is to obliterate only those files associated with projects within a specific entity-path, not the entire repository. Is there any way to do this?

[Beth]

At what level did the initial delete occur? If you deleted $/DotNet, then DotNet is the item that is ready to be obliterated.

Just as an FYI, Obliterate and Export/Import are not compatible. If you plant to use Export/Import on that repository, even on a different path, it will fail if Obliterates were performed on the repository.

I'm moving this thread over to the Development Tips (API) section.

[jeremy_sg]

My initial reaction to anyone asking about Obliterate is to discourage them. Obliterate is a long, complicated process, that usually doesn't free up all that much space. Basically, unless you have checked in 200MB binary files and you want to obliterate them, Obliterate is probably not worth it.

Secondly, why aren't you using the Admin Web Client, or the Advanced Obliterate Client power toy?

As for your question, can you post the code that you're using? ListDeletedObjects can only be used on items that are currently in the tree, and is not recursive by default.

[surak8]

I am unable to reproduce this issue following installation of 5.0.3.18802.

My code was:
const string repEnt="$/DotNet/AccountMaint";
ClientInstance ci=ServerOperations.client.ClientInstance;
VaultDeletedObject[] delObjs=ci.ListDeletedObjects(repEnt,true);

As far as Jeremy's comments and questions, the reason I was performing my own Obliterate was because:
1) there is no import utility for PVCS, so I was forced to write one..
2) After running my import utility (20-30 times), client/server performance seemed to degrade noticeably.
3) Obiliterate seemed to return normal speed to client/server.
4) Web client was too cumbersome, and did not know about power tool. No user interface was required for my need to Obliterate, as I needed to clean up old stuff, under a given project-path.

My $/DotNet/Account is a very simple project (see attached image), but $/DotNet/TradeCapture would have been MUCH more difficult clean.

[Beth]

Thanks for the update. I'm happy to hear it worked after the upgrade.