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

Question

Question

Form table lookup very slow

Forms
Updated January 13, 2020
asked on January 13, 2020

Hello,


I have a form that has a look up to populate a table. The SQL runs very quickly if I run a query manually and form loads quickly if I disable this rule. Do you have any suggestions to improve the speed of the lookup? It is taking about a minute to load. 

0 0

Replies

replied on January 13, 2020

I should have added, I'm on Forms  10.4.1.172. Thank you in advance. 

0 0
replied on January 13, 2020

How many results does the query return? Which browsers have you tested it in?

Based on my own experience, it is unlikely the query itself that is taking so much time, rather the delay is related to the time it takes to create the rows/columns of the table (i.e., the HTML elements on the form).

0 0
View 3 previous replies
replied on January 13, 2020

Hello,

We only have 2184 records at the moment.

0 0
replied on January 13, 2020

How many are actually being returned on the form? Depending on the browser, anything more than 100-200 is going to cause a noticeable performance hit.

2,184 doesn't seem like much from a data perspective, but web browsers really aren't designed to handle adding that many interactive elements to a single page.

1 0
replied on January 13, 2020

There are 43 returned on this specific student. I don't see the number growing over 180 for any given student. 

0 0
replied on January 13, 2020

Which browser are you using?

I would also try testing with only one or two of the columns to see how much of a difference it makes in performance.

43 rows shouldn't be "too" bad, but again, it depends on the browser and the resources on the PC you are using to view the page.

0 0
replied on January 13, 2020

I've tried Chrome and Edge and both are slow. I added a new table and changed the lookup to the new table and it's faster. It seems like it's working now. It's weird because nothing changed except it being an exact copy of the old table. 

0 0
replied on January 13, 2020

Interesting. Hard to say for sure what may have caused that, but I have read other posts where weird/unexpected issues have been solved by simply recreating the affected fields. If I had to guess I'd say either the table or lookup rule had some kind of issue; if I'm not mistaken, it creates a new lookup rule if you assign it to a different field or make other major changes, so I'd be curious to see if switching it back still yielded the same delays.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...