Cleaning Views to Remove the Virtual Folder

I created a View that will not show empty virtual folders.  This works well such that if there is no file tagged then the virtual folder will not be visible.

However, it doesn't work the other way.  When I have files that are in the virtual folder and I delete them, the virtual folder is still there.  Should this also go away automatically?

As a workaround, I am having to Right Click and 'Clean View' and then the Empty folders will be invisible again.

Is there a better way to do this instead of me selecting 'Clean View' on all the Views?

Parents
  • My best guess as to why the folder remains visible is twofold:

    1. the deleted file remains in the local cache on the client computer. When you use the Clean View function you are asked to confirm that temporary files can be deleted.
    2. deleted files are not really deleted in M-Files, they only get a flag that says they have been deleted. This creates a new version of the document. The old version still fulfills the requirements for showing the "deleted" document.

    1) can be resolved by deleting the cached data for that vault on the client computer.
    2) could be resolved by destroying the document rather than delete it.

    A quick test shows that 1) works, 2) does not.
    That means you can clean up all views by deleting the cache. However, it only works on the local client - you cannot do this in a centralized manner - at least not with simple tools. It would also suggest that the problem indeed is individual for each user. Most users won't notice the problem at all. So perhaps you should not worry too much about it.....

Reply
  • My best guess as to why the folder remains visible is twofold:

    1. the deleted file remains in the local cache on the client computer. When you use the Clean View function you are asked to confirm that temporary files can be deleted.
    2. deleted files are not really deleted in M-Files, they only get a flag that says they have been deleted. This creates a new version of the document. The old version still fulfills the requirements for showing the "deleted" document.

    1) can be resolved by deleting the cached data for that vault on the client computer.
    2) could be resolved by destroying the document rather than delete it.

    A quick test shows that 1) works, 2) does not.
    That means you can clean up all views by deleting the cache. However, it only works on the local client - you cannot do this in a centralized manner - at least not with simple tools. It would also suggest that the problem indeed is individual for each user. Most users won't notice the problem at all. So perhaps you should not worry too much about it.....

Children
No Data