#Hindustan epaper agra edition update#

I eventually realised that the report viewer control was not performing a full postback, but just a partial postback and that I needed to put the Label control inside an update panel.

#Hindustan epaper agra edition code#

Somehow or another the initial message was being set, however the changes in TheReport_ReportRefresh were not being applied despite me verifying the code was being run. Protected void TheReport_ReportRefresh(object sender, CancelEventArgs e) ReportErrorMessage.Text = BuildUnknownErrorMessage(e) ReportErrorMessage.Text = BuildBadParameterMessage(e) However, I found that while I could get the message to display initially, I could not get it to go away once the user had corrected the error.Ĭ# protected void TheReport_ReportError(object sender, ReportErrorEventArgs e) With that in mind I thought that what I’d do is create a Label on the page to hold the error message and populate it if an error occurred. There is a ReportError event that you can subscribe to and indicate you’ve handled the error, but no where to provide a better error message. In fact the control gives you no way to alter the error messages that it shows. Why should they even have to see things like that?

The nearest possibly alternative on the page reads “To Date” so they could possibly take a good guess, but why risk support calls over something like that? And the “(rsReportParameterTypeMismatch)” is likely to mean even less to a user. The value provided for the report parameter 'pToDate' is not valid for its type. One of the feedback items from the first round of user testing was that the error messages from the control were not helpful or friendly.įor example, if a user types in a date in an incorrect format the Report Viewer Control would return an error message to the user like this: For a project I’m working on I’ve got to display data that’s coming from SSRS (SQL Server Reporting Services) on a web page for our users.