Question

Possible to add delay to dynamic field results in Web Access 10?

Web Client Version 10

Updated March 1, 2016

asked on February 27, 2016

So here is the issue we are having. We have a SQL table with 5k rows, the dynamic field is very slow to respond and even causes some browsers to crash because the data starts with number vs alpha characters. Let me explain.

We have a field of vendor names, the data table is a similar size but because they entries start with alpha characters the second you type the first character the list becomes immediately much smaller. You are only getting all the A's for example.

However the field we are having issues with contains GL account numbers, so they look like 1-5-10000-10000, most start with 1,2,3 and even later numbers are normally the same, so you don't really start to narrow the list until you have gotten to 1-5-10 etc.

So what I am looking for is a way for LF Web Access to not actually try to query results until you have typed a certain number of characters into the field, so that by the time the first query is returned the length of results has already started to drop.

Ideally I would like this added as a feature, because on large data sets in web access the performance is abysmal. ie a setting for the number of characters before results are returned that can be set by the administrator.

This problem is currently holding up a project that has already been delayed for over a year waiting for Web Access 10. So in the meantime is there any thoughts anyone has on how I can work around this issue. I have thought of reordering the GL numbers etc, but all those things are pretty hokey and make the project look like a piece of junk to the end users that you have to do this hokey thing to make it work. We don't control the numbers they are set by Finance.

Thanks

Joel

0 0

Replies

replied on February 29, 2016

Have you tried the MaxDropDownLength setting? It allows you to set a limit on the length of the dynamic field dropdown so that it doesn't show until the user types enough to filter down the list.

1 0

replied on February 28, 2016

Hi Joel,

My first thought was to add an extra field to allow the user to select "1-1, 1-2...1-5" then the second field would show the filleted list. If this is your idea of hokey, then the another approach could be to determine if the 5k of GL numbers are all active or relevant to the every type of document. I'd look for a rule to create one or more views with smaller sets of GL numbers. The rules could even be calculated from other Laserfiche documents or values.

oes that sound like a possibility?

0 0

replied on February 29, 2016

In your database have there been any indexes on the table in question?

0 0

replied on February 29, 2016

Ben: No thats not really possible because this is for AP project and we don't know ahead of time where the items will be charge, capitol, operating etc, so we have to present all of them. Also its a multi value field, so parent child don't work, unless that issue has been fixed.

Blake: In the DB itself the return is instant, like milliseconds, so the problem doesn't seem to be inside the database.

Robert: We are already using maxdropdown. However it looks to me like it is all happening client side in the browser, and so the data is still returned to the browser all 5k records, and then its up to the browser to decide when to show the list. It doesn't look to me like the server is doing the heavy lifting. Which is why in IE when you type the first character it will crash sometimes.

If it was happening server side I don't think I would have any issues with it, right?

0 0

replied on February 29, 2016 • Show version history

Hi Joel,

According to the documentation, yes the multi value feature had been added. The lookup will only be filtered by the first item in the lookup.

Could you use Department to filter the GL codes?

0 0

replied on March 1, 2016

No unfortunately I can't use department either because there could be multiple departments GL #'s on the same invoice. I could add the department number to the beginning of the SQL field, but then the field gets so long that the useful data flows off the side of the page.

an an aside we did AP as our first workflow project. Don't ever do that it is the worst first project you could do, the number of exceptions outnumbers the number of rules :) Anything else would be easier.

1 0

You are not allowed to follow up in this post.

Question

Question

Possible to add delay to dynamic field results in Web Access 10?

Replies

Sign in to reply to this post.