I was working with a client on a quick fields issue, trying to get formatting to line up with a specific type of paper they use when I encountered some unusual behavior from post process border padding. I found that when post process border padding was applied, it would affect the quality of the Zone OCR significantly and manually entered metadata in quick fields would not save when the document was stored. I was also having an issue with the Count token incrementing by one after the document was stored. Removing post process border padding and adding it to the process itself resolved these issues and I don't understand why. They are using quick fields 9 and I did install the latest update, which made no change to the behavior. I tried to recreate the issue on my workstation but I was unable to do so. Has anyone else experience similar issues with Quick Fields 9?
Question
Question
Quick Fields metadata changes not saving when post process border padding is applied
Replies
Is anyone else using the same session (with border padding in post-processing) without issues? When you tried to reproduce the issue, did you use a copy of the customer's session or did you try to reproduce it in a different session?
No one else is using the session. When I tried to reproduce the issue, I created a new session. I will try importing their session onto my workstation and find out if I still have the same error
I imported the user's session into my workstation and tested the functionality with and without post process border padding, but I do not have the same issues that the user did. We are both using the same version of Quick Fields (9.0.1.496), but there are a couple of differences. One, that I am using capture engine to retrieve a sample document, whereas they are using an actual scanner. The other is that they are using Windows 10 and I am using Windows Server 2012. I should mention that they first began noticing the problem when their quick fields workstation was replaced with a Windows 10 machine. I am considering doing a repair of the Quick Fields installation, but I am reluctant to do so considering the problem has already been solved on their end.
I see, well feel free to let us know if the issue comes up again or you have any additional information.