Question

QF 9 possible bug

Version 9 Quick Fields

Updated March 11, 2015

asked on April 2, 2014

Using real-time lookup, we get our metadata from an ODBC connection using a barcoded unique ID:

The “If a field is blank” option was checked as this is how it was set under 8.3 and we are running the same session file. According to the blurb above, it should not be relevant as we’re not using LCE.

The metadata is found and the fields are populated

However, when the document is stored, the metadata is lost:

I un-checked the “If a field is blank…” checkbox: And the metadata is saved correctly when the document is stored:

0 0

Replies

replied on April 2, 2014

Are you on the most recent release of Quick Fields? There were some similar issues that have been hotfixed.

0 0

replied on July 23, 2014

If installing the latest hotfix fixed your issue, please click "This answered my question" next to Matt's post to let us know.

0 0

replied on February 24, 2015

I had the exact same issue I am using capture engine. I bring in the docs with no metadata and use zone ocr to populate the check number. Then I use lookup to populate the rest of the information. It works fine in QF but when I send the Docs it removes the metadata. If I uncheck the " If a field is blank.... " it works fine. I am running the most current version of QF. I was glad to find this post.

Thanks

0 0

replied on March 11, 2015

Installing QF 9.0 Hotfix 1013497 resolved this issue for us.

Been troubleshooting this issue today with the same QF process as Kyle’s (barcode>real-time lookup>populate metadata) and can verify that Matt’s recommendation of installing the latest hotfix (currently #1013497) corrected this issue.

Thanks Kyle for pinpointing the setting related to this issue and Matt for recognizing the resolution.

Original QF 9.0 install version:

QF 9.0 version with hotfix:

Zac

0 0

You are not allowed to follow up in this post.

Question

Question

QF 9 possible bug

Replies

Sign in to reply to this post.