

Independently from that you will name the scans, and in this dialogue you can pick a target folder as well. If you get the rename routine after each scan, or scan all in a batch depends on your settings. Since you will (probably) not throw all individual documents into one big pdf file, you will anyhow create small files. When I go through import folders, I do not scan directly into EN. You get the latest ScanSnap Manager here - pick your scanner, pick your OS, and it will take you to the installer: I think this is going to be one of the workflow changes that we will have to embrace or move to a different product which may not do scanning any better. The change in scanning with ScanSnap, for me, from Legacy has not been especially challenging since ScanSnap updated the Manager application to work with Evernote 10. One copy of the scanned document arrives in tyhe destination notebook as expected - no corrupted PDFs on the way.

However, when I have scanned to an Import Folder this has worked perfectly everytime. I generally scan direct to Evernote so my scans go to the default fold. My conclusion is that it does no good to scan directly into the import folder.Ĭlearly, the variety of configurations mean that we tend to have different experiences. It was corrupted because the scanner was still adding to that file.Īfter several bad imports, it finally created one good import from the import folder, which was the last version from the scanner. It contained nothing but a corrupted pdf file. The scanning was still going on, but the first note appeared. Why Evernote? Why are you doing this to me?Įdit: What happened to me when I scanned directly into the import folder was this. I had to use EN Legacy to screenclip this images. I'll try uninstalling 10.17 and see if Legacy will magically regain control of the ScanSnap import process which it has carried out properly for me since 2016.īTW, EN 10.17 doesn't have a screenclip option. How can I undo this holy mess 10.17 has wrought upon me? I went ahead and installed Legacy but when I scan a receipt, EN 10.17 greedily intercepts the scanning import process and puts it in the default user notebook, not the Receipts notebook that has been happily importing all these years prior to the 10.17 update (see attached screenclip).

(see screenclip) After upgrading to 10.17, ScanSnap scans just go to one notebook (the default user notebook) with the rest of my notes. In my old Evernote app, under Tools, there was a "ScanSnap Options." option which brought up options to auto-file scanned items from the Evernote ScanSnap Scanner to separate notebooks for Documents, Business Cards, Receipts and Photographs.
