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

Question

Question

Collection + pagination = speed?

asked on April 21

I have several severe issues after upgrading to version 12. It seems that field rules and lookups now take slightly slower to run and easily compound each other differently than version 11. Full disclosure: this has been my experience where many others have only seen the opposite. Woo hoo lucky us.

I have a collection that is pretty busy on a form since we cannot embed a table within a table nor collection within a collection.

What will happen if I use pagination on this troublesome collection? I read somewhere there is an advantage to using pagination on the form itself but can't find that resource to reference here. I wonder if setting the pagination on the collection might serve as cache of memory or some other advantage that could return my many users experience to stop loathing the use of Laserfiche Forms. Yes, I have a LF Support ticket in. 

The questions:
Has anyone noticed more speed using a collection with pagination?

Do your users regularly need more than 25 rows in a collection?

Do also you see a slow down after 25 rows in version 12?

 

Thank you 'fiche friends! 

 

 

0 0

Replies

replied on April 21

Pagination typically helps with rendering performance, i.e. instead of rendering 500-1000 fields the browser only renders 25-100. But field rules and formulas will run regardless at least internally (not displayed on the form). Its a non-destructive change you could try and see what effect it has on your form.

When I design forms I try to limit the amount of things the user has to see at one time as much as possible. Anything more than 5-10 rows of a table or 10-20 fields is impossible to parse. If they need to locate something they can use search/filters on the table/collection instead.

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

Sign in to reply to this post.