Note that there are some explanatory texts on larger screens.

plurals
  1. POReporting Services Interactive Sort and Paging Problem With ReportViewer
    primarykey
    data
    text
    <p>I have been having a strange problem with interactive sorting and paging within a ReportViewer that I can't figure out. I am using a local report definition and a ReportViewer control within an aspx page. I have AsynchRendering set to true. Everything seems to work fine except for this problem. Here are the steps to reproduce the problem:</p> <pre> (page 1 before all sorts) COL1 | COL2 a 1 c 3 b 2 </pre> <p>1) While on page 1, sort ascending on COL1 - sort is correct</p> <pre> (page 1) COL1 | COL2 a 1 b 2 c 3 </pre> <p>2) Navigate to page 2 - sort is correct</p> <pre> (page 2) COL1 | COL2 d 4 e 5 f 6 </pre> <p>3) Sort descending on column X (after doing this it automatically returns to page 1) - sort is correct</p> <pre> (page 1) COL1 | COL2 z 26 y 25 w 24 </pre> <p>4) Navigate to page 2 again - sort is incorrect; the data is is still sorted in ascending order as if the sort click while on page 2 never happened</p> <pre> (page 2) COL1 | COL2 d 4 e 5 f 6 </pre> <p>Other strange things:</p> <ul> <li>If i navigate to any other page except for page 2 from page 1, the sort order is correct, and if i navigate to page 2 from any other page except from page 1, the sort order is correct.</li> <li>If i set AsyncRendering to false, i don't have this problem at all. I need AsyncRendering set to true though.</li> <li>This problem only happens in IE6 and IE7. I doesn't happen in Firefox or Chrome.</li> <li>Here's the weirdest one => this problem only happens after i deploy to the web server. If i run it from Visual Studio 2008 development server on my computer, everything works perfectly without exception.</li> </ul> <p>This is a problem because the corp i work for pretty much only uses IE6/IE7, this sort feature is a requirement, and the page is too slow if i don't use AsyncRendering.</p> <p>Any help with this would be much appreciated.</p> <p>(comments from an answer i made before i had enough reputation to be able to comment): there is something else i noticed about what is happening with this. using fiddler, i watched the http request/responses on each sort click and navigation click, and i noticed that there is no http GET request when navigating from page 1 to page 2. all other navigation clicks and sort clicks make a GET request and then the html is refreshed with the corresponding response. if there is no GET request when navigating from page 1 to 2 after another sort has happened, then the page will not get refreshed to the current sort order. this seems like a ReportViewer AJAX bug to me...</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload