mzn developer
Top achievements
Rank 1
Rank 1
mzn developer
asked on 03 Sep 2008, 02:58 PM
Hello,
I've noticed some weird behavior with my grid with custom paging, and went to the demo site http://demos.telerik.com/aspnet/Grid/Examples/Programming/CustomPaging/DefaultVB.aspx located here, and was able to reproduce the bug.
Follow these steps to reproduce the bug:
1. Filter the first column by typing in "Number" and the filter by "Contains" (Notice the amount of pages after this first filter).
2. Filter the second column by typing in "10" and filter by "Equal To".
3. Remove the second column filter by deleting "10" and filter by "NoFilter".
Notice the resulting number of pages, it still says there is only one page of results, when it should be the same result set as after we applied #1.
Thank you for your assistance.
I've noticed some weird behavior with my grid with custom paging, and went to the demo site http://demos.telerik.com/aspnet/Grid/Examples/Programming/CustomPaging/DefaultVB.aspx located here, and was able to reproduce the bug.
Follow these steps to reproduce the bug:
1. Filter the first column by typing in "Number" and the filter by "Contains" (Notice the amount of pages after this first filter).
2. Filter the second column by typing in "10" and filter by "Equal To".
3. Remove the second column filter by deleting "10" and filter by "NoFilter".
Notice the resulting number of pages, it still says there is only one page of results, when it should be the same result set as after we applied #1.
Thank you for your assistance.
2 Answers, 1 is accepted
0
mzn developer
Top achievements
Rank 1
Rank 1
answered on 03 Sep 2008, 03:03 PM
I do realize that this is the ASP.Net demo, but the same bug occurs when using the AJAX.net version.
0
Hi,
Indeed looks like it's a bug in the example. You can try the second grid (which is bound to ObjectDataSource) where the behavior is correct.
Kind regards,
Vlad
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Indeed looks like it's a bug in the example. You can try the second grid (which is bound to ObjectDataSource) where the behavior is correct.
Kind regards,
Vlad
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.