Forms Lookup Rules Crashing

asked on August 13, 2021

Greetings,

I am implementing a Lookup Rule for one of my forms and noticed a bug that crashes/freezes the entire Forms Server (for me, not for other users) and the only way to fix the crash is to completely close and open my browser. Refreshing or closing the forms website specifically themselves will not fix this issue.

The attached screenshots are in order and show what happens.

I'll fill the email field that is used by the lookup rule to populate the first name and last name field.
Should I (the user) choose to change the email field (but not let it go blank, such as highlight the existing string, and paste something on it) the rule will still work and the name fields will update correctly.
Should I choose to make the email field blank after a lookup, the site crashes and no more lookups will occur.

To try to address the issue, I have modified my lookup rules with no luck. There are no overlapping rules either.

How can this be addressed? All help is greatly appreciated.

p1.JPG (13.92 KB)

| Download

p2.JPG (17.51 KB)

| Download

p3.JPG (17.13 KB)

| Download

0 0

replied on August 13, 2021

You said it only crashes your connection (doesn't affect other users), but does the same bug happen if you try to reproduce with another user?

After clearing out the input field, does the page crash immediately? Or only after you click out of the field? For instance, if you type John Deere's email, backspace to clear it, then type a new email all without clicking out, does it crash? Or does the new email work after clicking out?

It almost seems like you clear the input, click out, then the lookup runs and tries to return a ton of values into the fields as options. Do you have many many rows with a blank email it's trying to grab?

1 0

View 3 previous replies

replied on August 13, 2021

Yes the bug can be reproduced with other users.

The bug occurs when clicking out of the blank field.

If I clear John Deer's email, without clicking out, the bug does not happen.

If I clear the email (without clicking out) and input a new string (doesnt even have to be email format. literally a single character works), after clicking out, the bug will not occur and the other fields will be updated by the lookup (updates to blank if not email format).

As for your final paragraph, I am actually not sure about many records having blank email fields so I will look into this.

0 0

replied on August 13, 2021

Just checked with the person who wrote the stored procedure being used for the lookup rule.

He tested the function directly (not on LF Forms) with a blank parameter and the function returned an error. If it returns an error, this shouldn't be causing a connection crash. Should it?

0 0

SELECTED ANSWER

replied on August 13, 2021

Yes, that's causing the error you are seeing. You should update the stored procedure to handle the blank input so it returns a blank as opposed to an error.

0 0

replied on August 16, 2021

Thanks for the help Jared!

The stored procedure was updated and the error is no longer occurring!

0 0

replied on August 19, 2021

Sorry to piggyback off this Jared, but would you happen to know if this solution would be related to a similar bug occurring when using a separate lookup rule on a date field?

I tested several cases and noticed that my connection will crash when the string inside a date field has:

less characters than the date format being used (inputting less than 10 chars when format is MM-DD-YYYY)
has a month or day out of range (input '13' for the month or '32' for the day)

I'll be making a separate Answers post for this as well.

Thanks!

0 0

replied on August 19, 2021

If your lookup returns data that's invalid for the field you're trying to fill, that likely is the source of the problems.

0 0

Question

Question

Answer

Replies

Sign in to reply to this post.