DMXzone Action Scheduler Support Product Page
Not a problem
Does not work with paged recordsets?
Reported 11 May 2016 23:24:07
1
has this problem
11 May 2016 23:24:07 Brad Lawryk posted:
One a paged recordset there is two issues ...1: Each time the data refreshes it goes back to the first page
2: If using alerts with a paged recordset it shows an alert for the top record of each page
Replies
Replied 12 May 2016 08:04:11
12 May 2016 08:04:11 Teodor Kuduschiev replied:
Hello Brad,
Could you please be a little more detailed? Maybe provide a link to the page, where we can see your setup.
Could you please be a little more detailed? Maybe provide a link to the page, where we can see your setup.
Replied 12 May 2016 16:08:36
12 May 2016 16:08:36 Brad Lawryk replied:
I will send you a link with login credentials ...
Replied 13 May 2016 08:15:23
13 May 2016 08:15:23 Teodor Kuduschiev replied:
Hello Brad,
I've checked your page and saw a couple of issues.
1. You should set the records per page limit in the server connect executor, as explained here: www.dmxzone.com/go/32304/creating-a-paged-query/ and not like you are doing it now in the extended repeater.
2. You should be using the states manager, in order to keep your page, so when refreshing the data source it keeps the current page. That is why we released it: www.dmxzone.com/go/32362/keep-pagination-state-with-html5-data-bindings-state-management
As for responsive notify running for top records - i will check why/when this happens and will let you know how to fix it then.
I've checked your page and saw a couple of issues.
1. You should set the records per page limit in the server connect executor, as explained here: www.dmxzone.com/go/32304/creating-a-paged-query/ and not like you are doing it now in the extended repeater.
2. You should be using the states manager, in order to keep your page, so when refreshing the data source it keeps the current page. That is why we released it: www.dmxzone.com/go/32362/keep-pagination-state-with-html5-data-bindings-state-management
As for responsive notify running for top records - i will check why/when this happens and will let you know how to fix it then.