parameter behavior changes when we deselect defaults

db042190 1,516 Reputation points

Hi this is a little weird. We run 2014 enterprise.

We agreed with our user that for the 3 parameters in her new report, the first and second which are from and thru dates would not default and not allow nulls.

The 3rd parameter would default to "Both" for the 2 "types" of items that drop down before the word Both.

When deployed that way both date parameters were "open", ie not greyed out.

Our ops guy needed a quick way to stand up a non data driven subscription on this report so he asked us to put defaults in the first 2 params, deploy, create a linked report, hide the linked report and then in RM deselect "has default" for the first 2 params in the original report.

the problem is that now the 2nd date is greyed till the first date is filled in and then we click anywhere or hit "run report".

is there a way to avoid that extra click just like we experienced before defaults were added?

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,790 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Joyzhao-MSFT 15,566 Reputation points

    Hi @db042190 ,
    I am sorry that it is not enough clear for me to understand what your needs. From your description, it seems that the first two parameters are cascading parameters.
    Could you let me know your report structure and parameter settings with screenshots?
    Best Regards,

    0 comments No comments

  2. db042190 1,516 Reputation points

    thx Joy, they aren't cascaded. Shown below is all you should need to answer this question...there is only one dataset in the report and it depends on all 3 params.


    0 comments No comments