There is some technical issue with this whole sorting approach and not sure what we are doing wrong.
We are using MVC HTML5 viewer. The report has default values for report parameters that are used only in design. When the report is integrated in the application, we use JS methods to get the actual parameters and pass it to report. but when we click on the column header, the report displays with the default parameters and not with the parameters used last from the application.
I can see this via Fiddler and Network tab in browser that as soon as Column header is clicked, it makes a call to 'parameters' for the web-api with the default parameters instead of the last set of parameters that report was open with.
We tried with both persistSession-true/false but no luck. In the history of the session-storage, the first parameter is the default report parameters and then it stores the parameters as the report was refreshed or initialized with. I fail to understand why it uses the report's default parameters and how to tell it to not use it at all.