You are viewing limited content. For full access, please sign in.

Question

Question

Problem using lookup on .WAV files in Quick Fields 9.0.0.460

asked on March 7, 2014

We have a customer who has an LF Capture QF session that processes multiple file types, does a lookup on the document's name, and fills in multiple fields.  The session works great, except that on .WAV files, the lookup fills in lookup tokens rather than the returned value.  If you do the same lookup (same doc name), but as a different type of file, the lookup behaves correctly.  

 

Any idea why processing .WAV files would cause the lookup to behave that way?  Thanks very much!

0 0

Answer

SELECTED ANSWER
replied on March 10, 2014

A bug has been filed for the issue where the standard "Lookup" process doesn't seem to run on electronic documents (works fine for *.tif images). The workaround suggested above to use the "Field Lookup" real-time process should run correctly though.

2 0

Replies

replied on March 7, 2014

Are you using a Lookup process in the Page Processing stage?

1 0
replied on March 7, 2014

Ahhhh!  I bet that's what it is. I can't get a hold of the customer right now, but I will verify.  Thanks Miruna!

0 0
replied on March 10, 2014

I had them move around the Lookup, and they were unable to get it to work in any of the other areas either.  How do you recommend changing the configuration to accommodate for the WAVs?  Thanks very much! 

0 0
replied on March 10, 2014

I'd expect it to work in the Post-Processing stage. Have you tried using a Field Lookup instead?

0 0
replied on March 10, 2014

It didn't work in Post-Processing.  I'll see about Field Lookup and let you know.  Thanks!

0 0
SELECTED ANSWER
replied on March 10, 2014

A bug has been filed for the issue where the standard "Lookup" process doesn't seem to run on electronic documents (works fine for *.tif images). The workaround suggested above to use the "Field Lookup" real-time process should run correctly though.

2 0
replied on March 10, 2014

Thanks Alex!

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.