DMXzone App Connect Data Traversal Support Product Page
Answered
Server action delay using Data View
Asked 16 Nov 2018 14:55:22
1
has this question
16 Nov 2018 14:55:22 David Woolley posted:
I would like to use Data View to display records using the paging & filtering options in Data View.The Server Connect action does not have a filtered query, nor paging - all that happens client-side.
There are 3500 records in the database, and a delay of 13 secs before they are all loaded on the page.
I checked with Chrome Dev tools F12, and the server action is causing the delay of course.
When I set up a similar page that uses a server action with a filtered paged query without data view, the page loads the records instantaneously.
Any suggestions?
Replies
Replied 16 Nov 2018 16:07:52
16 Nov 2018 16:07:52 Teodor Kuduschiev replied:
Hi David,
It is recommended to use a paged query with huge amount of data, that loads slowly.
Data View is for smaller data sets.
It is recommended to use a paged query with huge amount of data, that loads slowly.
Data View is for smaller data sets.
Replied 16 Nov 2018 16:16:32
16 Nov 2018 16:16:32 David Woolley replied:
Thanks Teodor - I did not realize Data View had this limitation.
Is this documented on the DMXzone site?
Cheers
Dave
Is this documented on the DMXzone site?
Cheers
Dave
Replied 16 Nov 2018 16:21:39
16 Nov 2018 16:21:39 Teodor Kuduschiev replied:
It is not a limitation, it's how the component works.
Data View is a client-side data processing tool - meaning it loads ALL the data and then you sort, filter, search all client-side, without making a request to the server every time you do this.
A paged query however, runs on the server - every time you search, sort or filter you make a call to the server, the query runs and returns the result on the page.
When using data view a data source of about 2-3k records should be fine (depending on how many columns your table has of course). So for large data sources you just have to use the standard server side paged query ...
Data View is a client-side data processing tool - meaning it loads ALL the data and then you sort, filter, search all client-side, without making a request to the server every time you do this.
A paged query however, runs on the server - every time you search, sort or filter you make a call to the server, the query runs and returns the result on the page.
When using data view a data source of about 2-3k records should be fine (depending on how many columns your table has of course). So for large data sources you just have to use the standard server side paged query ...
Replied 16 Nov 2018 16:21:40
16 Nov 2018 16:21:40 Teodor Kuduschiev replied:
It is not a limitation, it's how the component works.
Data View is a client-side data processing tool - meaning it loads ALL the data and then you sort, filter, search all client-side, without making a request to the server every time you do this.
A paged query however, runs on the server - every time you search, sort or filter you make a call to the server, the query runs and returns the result on the page.
When using data view a data source of about 2-3k records should be fine (depending on how many columns your table has of course). So for large data sources you just have to use the standard server side paged query ...
Data View is a client-side data processing tool - meaning it loads ALL the data and then you sort, filter, search all client-side, without making a request to the server every time you do this.
A paged query however, runs on the server - every time you search, sort or filter you make a call to the server, the query runs and returns the result on the page.
When using data view a data source of about 2-3k records should be fine (depending on how many columns your table has of course). So for large data sources you just have to use the standard server side paged query ...