I've seen this question asked before, but have yet to see an adequate answer to why this happens. I'm aware of ruleIDs and triggerIDs, but that's not the issue. If you're displaying a form that has multiple lookup rules in play, the last event fired should NEVER be lookupstarted, EVER, right?! Somebody please explain to me how this happens or are the Laserfiche forms events simply not usable because they can't be relied upon?
Question
Question
Firing Order of lookupstarted and lookupcomplete events
Answer
Hi Eric,
What version of Forms are you using? There was a bug(167343) that lookupstarted/lookupcomplete sequence was wrong for lookup rule with multiple criterion fields and no auto fill button before 10.4.2. Is this same as your case?
If not, could kindly you describe the lookup rules having the issue so that we could try reproduce and investigate?
Hi Ziyan,
Our current version: Laserfiche Forms Professional Version 10.4.0.1256
The form in question has 5 lookup rules. 2 of those lookup rules have 2 criteria and "Show Auto Fill Button" NOT checked.
Then looks like it. I would also suggest upgrade to later version to have the fix in place.
Replies
We're now looking into getting our Forms implementation upgraded. In the meantime, I've checked the "Auto Fill Button" checkbox, hiding it with JavaScript, and running the autofill manually in a change event handler for the field in question. Now, the events fire properly. Thanks for the helpful comments guys.
Hi Eric,
As an aside, we would highly recommend upgrading your Forms instance to 10.4.5 (available through the Laserfiche 10.4.3 package) or to Forms 11 (available in the Laserfiche 11 package).
There have been quite a few important security updates since 10.4.0.