Question

lookup list length

Laserfiche Version 8 Version 9 Administration

Updated March 31, 2016

asked on May 12, 2014

I am debating whether to use a field text list or an SQL Dynamic field for a list of Client Codes.

There are 1500 codes which makes an extensive list. The text list is easier for the customer to amend in Admin console rather than having to edit in SQL.

Are there any issues with this length text list?

0 0

Answer

SELECTED ANSWER

replied on May 13, 2014

If you are concerned with performance of list/dynamic fields, I'd like to point out two new attributes related to drop-down list performance that were introduced in Laserfiche 9.0.2.

From the KB article List of Changes in Laserfiche 9.0.2:

You can now use the [Settings]CacheFieldValues and [Settings]MaxDropDownLength trustee attributes to control drop-down list behavior for list fields and dynamic fields. Set [Settings]CacheFieldValues to Yes to turn on caching for list fields and dynamic fields to speed up list re-loading. Enabling this attribute will also configure the Client to only retrieve list fields and dynamic fields once per client instance. Set [Settings]MaxDropDownLength to the maximum number of items to display in a drop-down list field or dynamic field. List fields longer than the limit will no longer automatically display all available items in the list until you enter enough characters for the auto-complete feature to retrieve a subset of list items. (98757)

1 0

View 1 previous reply

replied on March 29, 2016

Excuse me, where can I change those settings?

0 0

replied on March 30, 2016

Hi Christhian,

You have to add the "[Settings]MaxDropDownLength" as a User Attribute. I added it to the Everyone Group.

In Administration Console, open the user Everyone, select the Attributes tab and Add..

Set the attribute name to: [Settings]MaxDropDownLength

Set Data: to whatever length list you require. e.g. 10

Please note that it has a strange affect on lists. Normally as soon as you select a list or dynamic template field a list will appear. Now nothing will appear until you start typing a valid value.

0 0

replied on March 31, 2016

Thanks for your reply. My issue is that I have two dynamic fields querying a SQL table and it has about 9000 rows. Both fields are text type, but when i configure them dinamically they turn into list fields.

When I select the first field, the other is populated automatically but the selection in the first field is very tricky (the user has to type really fast the value, otherwise the wrong value is selected).

I'd like that the first field would remain text type and when I leave it the other field would be queried and bring the value. I have configured it succesfully in Laserfiche Forms but I see that it is not possible in Client.

0 0

Replies

replied on May 13, 2014

Large list fields introduce performance issues if you need to iterate into them. I personnally use a mixed approach where the 'master' list is an SQL table with a primary key for lookup purpose and a workflow that periodically updates the content of the list field. Unless the field is secured appropriately, you have to account for users adding values directly in the list field rather than its SQL counterpart.

1 0

replied on May 13, 2014

There is no problem in using the field text list.

And the advantage you could have is a quicker dropdown by using field text list instead of getting data from sql table (using dynamic fields), which makes the system slowdown if you are retrieving large number.

1 0

replied on May 13, 2014

Hello Uzair,

On what basis can you say «There is no problem in using the field text list»? The fact is: large list fields introduce performance issues if you need to iterate into them. Which is why Laserfiche 9.0.2 introduces the trustee attributes reported in Aaron's response. Take note CacheFieldValues is useless the first time you load the list field.

0 0

replied on June 22, 2014

Thank you all for your replies.

We elected to go with one large drop-down list field and it is working well..

Although there are 1600 fields, the search access etc. to the list is low so there are no performance issues. The list shows instantly as access to SQL is not required.

The large list is also reasonably easy to maintain as there would only be one or two additions per week.

1 0

You are not allowed to follow up in this post.

Question

Question

lookup list length

Answer

Replies

Sign in to reply to this post.