| Groups | Blog | Home |
sql server reporting services : URL Parameter and Default Values
I need to ability to pass a parameter (a session variable) on the URL that
will drive the content of parameters used for lookups. An example is that a person may be limited to only two districts out of 10, so for that person I only want the two districts show in the drop down list in the parameters section. Also, ideally I would not like the person number to be shown (or if shown read-only). I have tried several attempts using Report Manager and what I believe was fixed in SP1 (Readme Item 4.3.1 Hiding Parameters in Published Reports). Example: Reports Manager Parameter has following settings: Has Default (Checked) Default value (0) Prompt User (Unchecked) Prompt String (Not Set) http://servername/ReportServer?%2fFolder%2fItemList&pers_number=101 I get the following error response: "The report parameter 'pers_number' is read-only and cannot be modified" The report I am testing this with is displaying what would be shown in a parameter combo list, using the pers_number as its parameter. This will allow the simplest case to test this functionality with. If I check the Prompt User option, then the report runs displaying the correct content in my test report. In my real report with the above settings and the Prompt User option checked, the default value setting (0) is being passed as the parameter to the lookup stored procedure that fills another parameter and not the pers_number being passed on the URL line. Any help would be greatly appreciated! Mike
Make sure that the prompt user check box is checked but that the prompt
itself is empty. This should make your parameters hidden. Note that this can only be done through Report Manager and not through the designer. -- -Daniel This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "Michael McCallum" <mmccallum@honovi.net> wrote in message news:uKKC1ot8EHA.2012@TK2MSFTNGP15.phx.gbl... >I need to ability to pass a parameter (a session variable) on the URL that >will drive the content of parameters used for lookups. An example is that >a person may be limited to only two districts out of 10, so for that person >I only want the two districts show in the drop down list in the parameters >section. Also, ideally I would not like the person number to be shown (or >if shown read-only). I have tried several attempts using Report Manager >and what I believe was fixed in SP1 (Readme Item 4.3.1 Hiding Parameters in >Published Reports). > > Example: > Reports Manager Parameter has following settings: > Has Default (Checked) > Default value (0) > Prompt User (Unchecked) > Prompt String (Not Set) > > http://servername/ReportServer?%2fFolder%2fItemList&pers_number=101 > > I get the following error response: > "The report parameter 'pers_number' is read-only and cannot be modified" > > The report I am testing this with is displaying what would be shown in a > parameter combo list, using the pers_number as its parameter. This will > allow the simplest case to test this functionality with. If I check the > Prompt User option, then the report runs displaying the correct content in > my test report. > > In my real report with the above settings and the Prompt User option > checked, the default value setting (0) is being passed as the parameter to > the lookup stored procedure that fills another parameter and not the > pers_number being passed on the URL line. > > Any help would be greatly appreciated! > > Mike > > >
When do you receive this error?
-- -Daniel This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "Michael McCallum" <mmccallum@honovi.com> wrote in message news:uA768r18EHA.2276@TK2MSFTNGP09.phx.gbl... >I have done that part, but then get this error: "This report requires a >default or user-defined value for the report parameter 'p_pers_number'. To >run or subscribe to this report, you must provide a parameter value. >(rsReportParameterValueNotSet)" > > This parameter is used to limit another parameter lookup field. I am > thinking that this is where the error is being generated from. Any other > thoughts? > Mike > > > "Daniel Reib [MSFT]" <danreib@online.microsoft.com> wrote in message > news:uHksl$08EHA.2804@TK2MSFTNGP15.phx.gbl... >> Make sure that the prompt user check box is checked but that the prompt >> itself is empty. This should make your parameters hidden. Note that >> this can only be done through Report Manager and not through the >> designer. >> >> -- >> -Daniel >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> >> "Michael McCallum" <mmccallum@honovi.net> wrote in message >> news:uKKC1ot8EHA.2012@TK2MSFTNGP15.phx.gbl... >>>I need to ability to pass a parameter (a session variable) on the URL >>>that will drive the content of parameters used for lookups. An example >>>is that a person may be limited to only two districts out of 10, so for >>>that person I only want the two districts show in the drop down list in >>>the parameters section. Also, ideally I would not like the person number >>>to be shown (or if shown read-only). I have tried several attempts using >>>Report Manager and what I believe was fixed in SP1 (Readme Item 4.3.1 >>>Hiding Parameters in Published Reports). >>> >>> Example: >>> Reports Manager Parameter has following settings: >>> Has Default (Checked) >>> Default value (0) >>> Prompt User (Unchecked) >>> Prompt String (Not Set) >>> >>> http://servername/ReportServer?%2fFolder%2fItemList&pers_number=101 >>> >>> I get the following error response: >>> "The report parameter 'pers_number' is read-only and cannot be modified" >>> >>> The report I am testing this with is displaying what would be shown in a >>> parameter combo list, using the pers_number as its parameter. This will >>> allow the simplest case to test this functionality with. If I check the >>> Prompt User option, then the report runs displaying the correct content >>> in my test report. >>> >>> In my real report with the above settings and the Prompt User option >>> checked, the default value setting (0) is being passed as the parameter >>> to the lookup stored procedure that fills another parameter and not the >>> pers_number being passed on the URL line. >>> >>> Any help would be greatly appreciated! >>> >>> Mike >>> >>> >>> >> >> > >
I have done that part, but then get this error: "This report requires a
default or user-defined value for the report parameter 'p_pers_number'. To run or subscribe to this report, you must provide a parameter value. (rsReportParameterValueNotSet)" This parameter is used to limit another parameter lookup field. I am thinking that this is where the error is being generated from. Any other thoughts? Mike [quoted text, click to view] "Daniel Reib [MSFT]" <danreib@online.microsoft.com> wrote in message news:uHksl$08EHA.2804@TK2MSFTNGP15.phx.gbl... > Make sure that the prompt user check box is checked but that the prompt > itself is empty. This should make your parameters hidden. Note that this > can only be done through Report Manager and not through the designer. > > -- > -Daniel > This posting is provided "AS IS" with no warranties, and confers no > rights. > > > "Michael McCallum" <mmccallum@honovi.net> wrote in message > news:uKKC1ot8EHA.2012@TK2MSFTNGP15.phx.gbl... >>I need to ability to pass a parameter (a session variable) on the URL that >>will drive the content of parameters used for lookups. An example is that >>a person may be limited to only two districts out of 10, so for that >>person I only want the two districts show in the drop down list in the >>parameters section. Also, ideally I would not like the person number to >>be shown (or if shown read-only). I have tried several attempts using >>Report Manager and what I believe was fixed in SP1 (Readme Item 4.3.1 >>Hiding Parameters in Published Reports). >> >> Example: >> Reports Manager Parameter has following settings: >> Has Default (Checked) >> Default value (0) >> Prompt User (Unchecked) >> Prompt String (Not Set) >> >> http://servername/ReportServer?%2fFolder%2fItemList&pers_number=101 >> >> I get the following error response: >> "The report parameter 'pers_number' is read-only and cannot be modified" >> >> The report I am testing this with is displaying what would be shown in a >> parameter combo list, using the pers_number as its parameter. This will >> allow the simplest case to test this functionality with. If I check the >> Prompt User option, then the report runs displaying the correct content >> in my test report. >> >> In my real report with the above settings and the Prompt User option >> checked, the default value setting (0) is being passed as the parameter >> to the lookup stored procedure that fills another parameter and not the >> pers_number being passed on the URL line. >> >> Any help would be greatly appreciated! >> >> Mike >> >> >> > >
I put the following after the report name in the URL:
&p_pers_number=101&p_paco_code=7125 Which would set the two session variable entries, that are used to filter the other parameters. As soon as I hit enter, the toolbar returns with the two parameters that I want to pick of the list disabled and shows the green circle like it is executing the report. At this point is where the message is returned. The functionality I was looking to have is that the two remaining parameters in the Toolbar would contain the data from their stored procedure call, having the two URL parameters being passed to the stored procedure. I would then expect to see a filtered list of parameters based on the priv level of the user. Thanks... [quoted text, click to view] "Daniel Reib [MSFT]" <danreib@online.microsoft.com> wrote in message news:%23I1bHT28EHA.3476@TK2MSFTNGP15.phx.gbl... > When do you receive this error? > > -- > -Daniel > This posting is provided "AS IS" with no warranties, and confers no > rights. > > > "Michael McCallum" <mmccallum@honovi.com> wrote in message > news:uA768r18EHA.2276@TK2MSFTNGP09.phx.gbl... >>I have done that part, but then get this error: "This report requires a >>default or user-defined value for the report parameter 'p_pers_number'. To >>run or subscribe to this report, you must provide a parameter value. >>(rsReportParameterValueNotSet)" >> >> This parameter is used to limit another parameter lookup field. I am >> thinking that this is where the error is being generated from. Any other >> thoughts? >> Mike >> >> >> "Daniel Reib [MSFT]" <danreib@online.microsoft.com> wrote in message >> news:uHksl$08EHA.2804@TK2MSFTNGP15.phx.gbl... >>> Make sure that the prompt user check box is checked but that the prompt >>> itself is empty. This should make your parameters hidden. Note that >>> this can only be done through Report Manager and not through the >>> designer. >>> >>> -- >>> -Daniel >>> This posting is provided "AS IS" with no warranties, and confers no >>> rights. >>> >>> >>> "Michael McCallum" <mmccallum@honovi.net> wrote in message >>> news:uKKC1ot8EHA.2012@TK2MSFTNGP15.phx.gbl... >>>>I need to ability to pass a parameter (a session variable) on the URL >>>>that will drive the content of parameters used for lookups. An example >>>>is that a person may be limited to only two districts out of 10, so for >>>>that person I only want the two districts show in the drop down list in >>>>the parameters section. Also, ideally I would not like the person >>>>number to be shown (or if shown read-only). I have tried several >>>>attempts using Report Manager and what I believe was fixed in SP1 >>>>(Readme Item 4.3.1 Hiding Parameters in Published Reports). >>>> >>>> Example: >>>> Reports Manager Parameter has following settings: >>>> Has Default (Checked) >>>> Default value (0) >>>> Prompt User (Unchecked) >>>> Prompt String (Not Set) >>>> >>>> http://servername/ReportServer?%2fFolder%2fItemList&pers_number=101 >>>> >>>> I get the following error response: >>>> "The report parameter 'pers_number' is read-only and cannot be >>>> modified" >>>> >>>> The report I am testing this with is displaying what would be shown in >>>> a parameter combo list, using the pers_number as its parameter. This >>>> will allow the simplest case to test this functionality with. If I >>>> check the Prompt User option, then the report runs displaying the >>>> correct content in my test report. >>>> >>>> In my real report with the above settings and the Prompt User option >>>> checked, the default value setting (0) is being passed as the parameter >>>> to the lookup stored procedure that fills another parameter and not the >>>> pers_number being passed on the URL line. >>>> >>>> Any help would be greatly appreciated! >>>> >>>> Mike >>>> >>>> >>>> >>> >>> >> >> > >
Well it certainly looks like you are doing everything correct. I am not sure
at this point what the issue may be. You may want to think about contacting PSS at this point. -- -Daniel This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "Michael McCallum" <mmccallum@honovi.com> wrote in message news:%23YrEHu28EHA.1292@TK2MSFTNGP10.phx.gbl... >I put the following after the report name in the URL: >&p_pers_number=101&p_paco_code=7125 > > Which would set the two session variable entries, that are used to filter > the other parameters. As soon as I hit enter, the toolbar returns with > the two parameters that I want to pick of the list disabled and shows the > green circle like it is executing the report. At this point is where the > message is returned. > > The functionality I was looking to have is that the two remaining > parameters in the Toolbar would contain the data from their stored > procedure call, having the two URL parameters being passed to the stored > procedure. I would then expect to see a filtered list of parameters based > on the priv level of the user. > > Thanks... > > > "Daniel Reib [MSFT]" <danreib@online.microsoft.com> wrote in message > news:%23I1bHT28EHA.3476@TK2MSFTNGP15.phx.gbl... >> When do you receive this error? >> >> -- >> -Daniel >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> >> "Michael McCallum" <mmccallum@honovi.com> wrote in message >> news:uA768r18EHA.2276@TK2MSFTNGP09.phx.gbl... >>>I have done that part, but then get this error: "This report requires a >>>default or user-defined value for the report parameter 'p_pers_number'. >>>To run or subscribe to this report, you must provide a parameter value. >>>(rsReportParameterValueNotSet)" >>> >>> This parameter is used to limit another parameter lookup field. I am >>> thinking that this is where the error is being generated from. Any >>> other thoughts? >>> Mike >>> >>> >>> "Daniel Reib [MSFT]" <danreib@online.microsoft.com> wrote in message >>> news:uHksl$08EHA.2804@TK2MSFTNGP15.phx.gbl... >>>> Make sure that the prompt user check box is checked but that the prompt >>>> itself is empty. This should make your parameters hidden. Note that >>>> this can only be done through Report Manager and not through the >>>> designer. >>>> >>>> -- >>>> -Daniel >>>> This posting is provided "AS IS" with no warranties, and confers no >>>> rights. >>>> >>>> >>>> "Michael McCallum" <mmccallum@honovi.net> wrote in message >>>> news:uKKC1ot8EHA.2012@TK2MSFTNGP15.phx.gbl... >>>>>I need to ability to pass a parameter (a session variable) on the URL >>>>>that will drive the content of parameters used for lookups. An example >>>>>is that a person may be limited to only two districts out of 10, so for >>>>>that person I only want the two districts show in the drop down list in >>>>>the parameters section. Also, ideally I would not like the person >>>>>number to be shown (or if shown read-only). I have tried several >>>>>attempts using Report Manager and what I believe was fixed in SP1 >>>>>(Readme Item 4.3.1 Hiding Parameters in Published Reports). >>>>> >>>>> Example: >>>>> Reports Manager Parameter has following settings: >>>>> Has Default (Checked) >>>>> Default value (0) >>>>> Prompt User (Unchecked) >>>>> Prompt String (Not Set) >>>>> >>>>> http://servername/ReportServer?%2fFolder%2fItemList&pers_number=101 >>>>> >>>>> I get the following error response: >>>>> "The report parameter 'pers_number' is read-only and cannot be >>>>> modified" >>>>> >>>>> The report I am testing this with is displaying what would be shown in >>>>> a parameter combo list, using the pers_number as its parameter. This >>>>> will allow the simplest case to test this functionality with. If I >>>>> check the Prompt User option, then the report runs displaying the >>>>> correct content in my test report. >>>>> >>>>> In my real report with the above settings and the Prompt User option >>>>> checked, the default value setting (0) is being passed as the >>>>> parameter to the lookup stored procedure that fills another parameter >>>>> and not the pers_number being passed on the URL line. >>>>> >>>>> Any help would be greatly appreciated! >>>>> >>>>> Mike >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |