Replicatable bug with Detect New Files to Add

[dsmith]

Load the Detect New Files to Add dialog and check a folder, find a file that has been checked, go to windows explorer and delete that file then return to Detect New Files and change to another folder, you get an unhandled exception.

This is a useful excercise to find out which folders have files that shouldn't be there, to allow you to either delete them or add them to Vault. It would be much easier to have the option to hide excluded files, thus allowing you to pick out the new files easily.

Also, empty sub folders are always checked even though there is nothing in them to add to Vault.

[lbauer]

What version of the Vault client are you using?

[lbauer]

Never mind, I see this in 3.0.7 and 3.1.

Thanks for the report.

Maybe Detect New Files should have an option to delete unwanted files from the working folder as well as to add new files, so you don't have to go back into Windows Explorer to do the deletion?

I think we've already got a request logged for the option to not show excluded files at all.

[dsmith]

Version 3.0.7 (2863)

[GregM]

Maybe Detect New Files should have an option to delete unwanted files from the working folder as well as to add new files, so you don't have to go back into Windows Explorer to do the deletion?

That would be nice. I do this now by using a folder diff, but that takes a long time to start up because it has to build the baseline, and we have a large tree. Some of the unwanted files were never in Vault, so the automatic delete option wouldn't help here.

[lbauer]

I'll log a feature request for the option to delete any new files detected by the Detect New Files to Add function.

[gsmalter]

I am experiencing the originally described problem in version 3.1.2 of the client.