Question

Real Time Lookup inconsistent after 10.1 upgrade.

Quick Fields Version 10

Updated August 1, 2017

asked on May 30, 2017 • Show version history

We just upgraded a series of Quick Fields machines from 8.3.1 to 10.1, using sessions with Real Time Look Up.

Our key value is a claim number, from which we then populate eight other fields. It is a process that has worked without issue for years.

The problem is that the fields do not all populate at the same time. Most of the fields populate as soon as we enter the claim number. But two fields do not populate until we move to the next document.

Our triggers are: 1) When the Claim Number changes, and 2) When the document is processed. It seems to only be populating the two fields on the last trigger. So we get our data, but it is annoying.

We have removed and then added the fields we want back into the session, added other field changes as a trigger, but nothing is solving this.

Has anyone else seen this issue? if so, how did you solve it?

TIA -

0 0

Answer

SELECTED ANSWER

replied on July 28, 2017

Hi Bill!

A hotfix for bug #28832 is now available for Quick Fields 10.1. See KB 1013873

0 0

replied on August 1, 2017

Great, thanks much!

0 0

Replies

replied on June 5, 2017 • Show version history

What kind of fields are these? We have a known issue with populating List Fields in a RT lookup.

Edit: I incorrectly thought there was also an issue with List Fields as a trigger for RT lookup

0 0

replied on June 6, 2017

Hi Peter - The trigger field is a text field, and the fields that do not populate with the others are both list fields. These are the only list fields we are populating with the RTL, so it's probably the issue you mentioned. Thanks for the info -

Bill

0 0

replied on June 6, 2017 • Show version history

OK sounds like our issue then. You can reference it with TFS #28832 if you're interested.

There's a workaround that's a little annoying. After you run the RT lookup (and see the other fields populate) you can:

1. Click into the trigger field again

2. Click away from the document (so that you do not see the fields anymore). I'd recommend into Document Manager or a root folder so there's less time loading data.

3. Click back into the document

and the List Field should be populated from the lookup

This is definitely not ideal, though

1 0

replied on June 7, 2017

Thanks, Peter - This is the behavior we saw. It looks like the field change trigger is not fired, but the "When Document is Processed" trigger does fire, once the user moves off of the document. We did not try simply sending the document into Laserfiche, but I suspect that would have filled in the field as well.

0 0

You are not allowed to follow up in this post.

Question

Question

Real Time Lookup inconsistent after 10.1 upgrade.

Answer

Replies

Sign in to reply to this post.