Saving from Chrome PDF viewer to MFiles

I suggest you bring this up with our support department (support@m-files.com) who will be able to investigate further and/or tell you if this is a known issue and any workarounds.

Regards,

Craig.

I had this issue somewhere a year ago, it hasn't been fixed.

I submitted the issue to MFiles support and received the response below. There is a bug id open for the issue.

Good Afternoon Michelle

Thank you for contacting our Support Department. With regards to saving from the web browser, the reason you see the crdownload file is because that is a Chrome file placeholder as it is streaming the file down from the browser (before it is fully saved as a single file). The issue happens when you save directly to the M:\ and Chrome saves that placeholder prior to building the file. M-Files senses the crdownload as the actual file and tries to save metadata to it, only to be saved off in the vault as a "temporary file" that hasn't converted into an object.

Due to this behavior, the best method to handle this is to save to your local disk first, then transfer the actual downloaded file into the vault. This is recognized and logged in as a bug request with our developers under bug ID #18015.

To clear out the temporary file, go to the Home screen in the M-Files client, and you will see a heading labeled "Other". Expand it and you will see greyed out files. Those are the temporary files, one of which likely is the PDF you tried to save. Simply delete/destroy them so you can add a clean one back into the vault.


***************************************
Best Regards,


M-Files Customer Support