SSRS ReportViewer Control with Drop-down List Parameter Values Selects the wrong value

Stewart, Beth 86 Reputation points
2020-11-19T21:06:19.867+00:00

Hello. I am having problems with reports that are viewed using the SSRS ReportViewer for web forms. We are using the latest version of Microsoft.ReportingServices.ReportViewerControl, v150.1404.0.

If a report has a parameter that is populated with values and displayed with a drop-down list, the first time the report is loaded and a selection is made will result in the wrong item being selected. This will only occur if the parameter does not have a default value, causing the dropdown list to initially display the text "Select a Value."

Here are pictures illustrating the problem. These screenshots are again not from within SSRS, but when viewing a report using the ReportViewer control within a web forms site. This problem does not occur when the report is viewed in SSRS.

41136-reportparameterproblem1.png

Next, I will try to select the third item on the list of available values.

41212-reportparameterproblem2.png

After I make the selectiong ("Digital Humanities"), the dropdown list displays that I have selected the item that is the fourth item on the list, as shown here:

41186-reportparameterproblem3.png

Once the report has been run by clicking "View Report," the issue is eliminated, but the report will run with the wrong parameter value. The user can then select the correct value and run the report again; the dropdown list will now function correctly.

This issue has been replicated in Edge, Chrome, and IE.

SQL Server Reporting Services
SQL Server Reporting Services
A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
2,972 questions
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. ZoeHui-MSFT 39,671 Reputation points
    2020-11-20T09:15:09.597+00:00

    Hi @Stewart, Beth ,

    Suppose that you are using ReportViewer Control for developing.

    Could you have a check if your workmates also have this issue to see if it's a general issue.

    There is something wrong with my pc, I'll repair it and do the test as well later.

    I'm not familiar with develop.

    I'd like suggesting that you may also raise the question to asp.net to see if there will be more message for you.

    https://forums.asp.net/

    Regards,
    Zoe


    If the answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    What can I do if my transaction log is full?--- Hot issues November

    How to convert Profiler trace into a SQL Server table -- Hot issues November

    0 comments No comments

  2. Stewart, Beth 86 Reputation points
    2020-11-20T20:46:51.95+00:00

    Thanks for the response. The issue is existing for everyone using our software - about a thousand office users across multiple browsers. The odd thing is that we've used the Report Viewer control for years without issue. This appears to be a new problem.

    0 comments No comments

  3. ZoeHui-MSFT 39,671 Reputation points
    2020-11-23T05:51:19.717+00:00

    Hi @Stewart, Beth ,

    I tested locally today and I couldn't reproduce the issue.

    My visual studio is v2017.

    I used the ReportViewerControl v150.1404.0 and v150.900.148, everything goes well.

    Could you please create a simple report for test or have a check for the webform design.

    Regards,
    Zoe


    If the answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    What can I do if my transaction log is full?--- Hot issues November

    How to convert Profiler trace into a SQL Server table -- Hot issues November

    0 comments No comments

  4. Stewart, Beth 86 Reputation points
    2021-03-02T20:06:15.347+00:00

    Just to wrap up this item: it was discovered that this issue was caused by placing the reportViewer within a page with other style sheets that caused the problem. It resolved by placing the report viewer in an empty Asp.Net web form with no master files/extra styles.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.