Parameter menu hidden

Hi,
When I navigate to a report, the parameter menu is hidden. I have to
click on the arrows in the menu to unhide them. This only happens on
deployed reports viewing through IE. The navigate action is set to use:
"Jump to report". I could use "Jump to URL" but don't want to hardcode
the full URL.
The VS dev environment shows the parameter menu like it should in the
preview pane.
Anyone know how what to change so the parameter list is not hidden in
IE.
Asim.Anyone? I'm thinkings its a configuration change somewhere.
Any help would be appreciated.
Asim.
Asim wrote:
> Hi,
> When I navigate to a report, the parameter menu is hidden. I have to
> click on the arrows in the menu to unhide them. This only happens on
> deployed reports viewing through IE. The navigate action is set to use:
> "Jump to report". I could use "Jump to URL" but don't want to hardcode
> the full URL.
> The VS dev environment shows the parameter menu like it should in the
> preview pane.
> Anyone know how what to change so the parameter list is not hidden in
> IE.
> Asim.|||Thanks for replying. None of them have "Hide" checked. Also if I go to
the report directly in IE, the parameter menu is NOT hidden. This only
happens when I use the Navigate function in a text box to go to another
report, that the whole parameter menu is hidden.
Asim.
On Jan 24, 5:41 am, Amarnath <Amarn...@.discussions.microsoft.com>
wrote:
> Just go from Report Manager to that particular report and select properties
> from the tab. select parameters and check whether the "Hide" check box is
> checked, click accordingly and save and then check.
> Amarnath
>
> "Asim" wrote:
> > Anyone? I'm thinkings its a configuration change somewhere.
> > Any help would be appreciated.
> > Asim.
> > Asim wrote:
> > > Hi,
> > > When I navigate to a report, the parameter menu is hidden. I have to
> > > click on the arrows in the menu to unhide them. This only happens on
> > > deployed reports viewing through IE. The navigate action is set to use:
> > > "Jump to report". I could use "Jump to URL" but don't want to hardcode
> > > the full URL.
> > > The VS dev environment shows the parameter menu like it should in the
> > > preview pane.
> > > Anyone know how what to change so the parameter list is not hidden in
> > > IE.
> > > Asim.- Hide quoted text -- Show quoted text -|||I think this behaviour is by design. I thought you are just accesing a
report. Ok so you want a drilldown report. infact the purpose of drilldown is
to go to other report directly without entering anything, that's why the
parameter is not visible.
Amarnath
"Asim" wrote:
> Thanks for replying. None of them have "Hide" checked. Also if I go to
> the report directly in IE, the parameter menu is NOT hidden. This only
> happens when I use the Navigate function in a text box to go to another
> report, that the whole parameter menu is hidden.
> Asim.
>
> On Jan 24, 5:41 am, Amarnath <Amarn...@.discussions.microsoft.com>
> wrote:
> > Just go from Report Manager to that particular report and select properties
> > from the tab. select parameters and check whether the "Hide" check box is
> > checked, click accordingly and save and then check.
> >
> > Amarnath
> >
> >
> >
> > "Asim" wrote:
> > > Anyone? I'm thinkings its a configuration change somewhere.
> > > Any help would be appreciated.
> >
> > > Asim.
> >
> > > Asim wrote:
> > > > Hi,
> >
> > > > When I navigate to a report, the parameter menu is hidden. I have to
> > > > click on the arrows in the menu to unhide them. This only happens on
> > > > deployed reports viewing through IE. The navigate action is set to use:
> > > > "Jump to report". I could use "Jump to URL" but don't want to hardcode
> > > > the full URL.
> >
> > > > The VS dev environment shows the parameter menu like it should in the
> > > > preview pane.
> > > > Anyone know how what to change so the parameter list is not hidden in
> > > > IE.
> >
> > > > Asim.- Hide quoted text -- Show quoted text -
>

parameter is missing a value.

Hi Friends,

I have created a child report with hidden parameter. When I call this report from the Master report using a link, I am getting error 'the xxxx parameter is missing a value'.

From, master report, if I click a value, it should take that value to child report where it filters for that value and should display the child report.

How to overcome this?

Thanks & Regards,

Naveen J V

Have you set any default value for the parameter in your subreport?

|||

Hi,

No default value has been set.

Regards,

Naveen J V

|||Ok, then try giving a default value for your hidden parameter. Give the same expression that you have used in the value field for the parameter. This might work. Not sure.|||

Hi,

I already tried this option, but I'm still getting the same error.

Thanks & Regards,

Naveen

|||

All the parameters created in sub-report should get some value, so if you have more than one parameter in the sub-report and from the master report you are passing value of only one parameter then obviously the value of other parameters will be missing. I suggest you to set the default value for the parameters in the sub report, so that the report get displayed even if you are passing wrong values from the master report.

By the way what is the expression that you are passing? And how many parameters you have?

|||

Hi Rohit,

My sub report has only one parameter. In my master report, If I click a particular column, it should take me to the sub report, where I should be able to see the filtered report based on the passed value.

It is working for one of my report which uses a different cube.

Thanks & Regards,

Naveen

|||

Can you give the expression that you are passing?

|||

Rohit,

While creating a report, in Query builder I selected a parameter (which referes to a member of a dimension). Same parameter I'm using in my report. I am not using any expressions.

Thanks & Regards,

Naveen

|||

what is the expression you are writting in the navigation properties for the parameter of your sub report?

|||

Hi,

Jump to Report ->Sub_rpt (sub report name)

Parameter name -> DLVLTM

Parameter value -> =Fields!TM.Uniquename

Regards,

Naveen J V

|||

Actually everything seems to be fine. It may be a data issue though.

anyways again give it a try:

Go to Sub report and in the report parameter window try by making available values non-queried.

|||

Hi Rohit,

If I dont hide the parameter, the report works fine. If I hide, only then I get this error. In the present context, it should be hidden. Based on the selection made from the master report, it should disply the child report.

I dont understand wht could be the problem?

Regards,

Naveen

|||

Hi Rohit,

I'm getting the same error. Please refer to my rprevious mail.

Regards,

Naveen J V

parameter is missing a value.

Hi Friends,

I have created a child report with hidden parameter. When I call this report from the Master report using a link, I am getting error 'the xxxx parameter is missing a value'.

From, master report, if I click a value, it should take that value to child report where it filters for that value and should display the child report.

How to overcome this?

Thanks & Regards,

Naveen J V

Have you set any default value for the parameter in your subreport?

|||

Hi,

No default value has been set.

Regards,

Naveen J V

|||Ok, then try giving a default value for your hidden parameter. Give the same expression that you have used in the value field for the parameter. This might work. Not sure.|||

Hi,

I already tried this option, but I'm still getting the same error.

Thanks & Regards,

Naveen

|||

All the parameters created in sub-report should get some value, so if you have more than one parameter in the sub-report and from the master report you are passing value of only one parameter then obviously the value of other parameters will be missing. I suggest you to set the default value for the parameters in the sub report, so that the report get displayed even if you are passing wrong values from the master report.

By the way what is the expression that you are passing? And how many parameters you have?

|||

Hi Rohit,

My sub report has only one parameter. In my master report, If I click a particular column, it should take me to the sub report, where I should be able to see the filtered report based on the passed value.

It is working for one of my report which uses a different cube.

Thanks & Regards,

Naveen

|||

Can you give the expression that you are passing?

|||

Rohit,

While creating a report, in Query builder I selected a parameter (which referes to a member of a dimension). Same parameter I'm using in my report. I am not using any expressions.

Thanks & Regards,

Naveen

|||

what is the expression you are writting in the navigation properties for the parameter of your sub report?

|||

Hi,

Jump to Report ->Sub_rpt (sub report name)

Parameter name -> DLVLTM

Parameter value -> =Fields!TM.Uniquename

Regards,

Naveen J V

|||

Actually everything seems to be fine. It may be a data issue though.

anyways again give it a try:

Go to Sub report and in the report parameter window try by making available values non-queried.

|||

Hi Rohit,

If I dont hide the parameter, the report works fine. If I hide, only then I get this error. In the present context, it should be hidden. Based on the selection made from the master report, it should disply the child report.

I dont understand wht could be the problem?

Regards,

Naveen

|||

Hi Rohit,

I'm getting the same error. Please refer to my rprevious mail.

Regards,

Naveen J V

parameter is missing a value.

Hi Friends,

I have created a child report with hidden parameter. When I call this report from the Master report using a link, I am getting error 'the xxxx parameter is missing a value'.

From, master report, if I click a value, it should take that value to child report where it filters for that value and should display the child report.

How to overcome this?

Thanks & Regards,

Naveen J V

Have you set any default value for the parameter in your subreport?

|||

Hi,

No default value has been set.

Regards,

Naveen J V

|||Ok, then try giving a default value for your hidden parameter. Give the same expression that you have used in the value field for the parameter. This might work. Not sure.|||

Hi,

I already tried this option, but I'm still getting the same error.

Thanks & Regards,

Naveen

|||

All the parameters created in sub-report should get some value, so if you have more than one parameter in the sub-report and from the master report you are passing value of only one parameter then obviously the value of other parameters will be missing. I suggest you to set the default value for the parameters in the sub report, so that the report get displayed even if you are passing wrong values from the master report.

By the way what is the expression that you are passing? And how many parameters you have?

|||

Hi Rohit,

My sub report has only one parameter. In my master report, If I click a particular column, it should take me to the sub report, where I should be able to see the filtered report based on the passed value.

It is working for one of my report which uses a different cube.

Thanks & Regards,

Naveen

|||

Can you give the expression that you are passing?

|||

Rohit,

While creating a report, in Query builder I selected a parameter (which referes to a member of a dimension). Same parameter I'm using in my report. I am not using any expressions.

Thanks & Regards,

Naveen

|||

what is the expression you are writting in the navigation properties for the parameter of your sub report?

|||

Hi,

Jump to Report ->Sub_rpt (sub report name)

Parameter name -> DLVLTM

Parameter value -> =Fields!TM.Uniquename

Regards,

Naveen J V

|||

Actually everything seems to be fine. It may be a data issue though.

anyways again give it a try:

Go to Sub report and in the report parameter window try by making available values non-queried.

|||

Hi Rohit,

If I dont hide the parameter, the report works fine. If I hide, only then I get this error. In the present context, it should be hidden. Based on the selection made from the master report, it should disply the child report.

I dont understand wht could be the problem?

Regards,

Naveen

|||

Hi Rohit,

I'm getting the same error. Please refer to my rprevious mail.

Regards,

Naveen J V

Parameter bug in Service Pack 1

I'm just curious if Microsoft has officially recognized the bug in Service
Pack 1, where attempting to pass a hidden and a prompted variable to a
report generates a Javascript "Object expected" error.
Or is this still being researched? Anyone?
BrianWe are aware of this. It is a bug. It happens when a parameter that you
hide would normally have a null check box. If you can set the parameter to
non-nullable, that will fix the problem. Otherwise, there is no workaround.
--
This posting is provided "AS IS" with no warranties, and confers no rights
"G" <brian.grant@.si-intl-kc.com> wrote in message
news:eJaxcCMdEHA.2752@.TK2MSFTNGP12.phx.gbl...
> I'm just curious if Microsoft has officially recognized the bug in Service
> Pack 1, where attempting to pass a hidden and a prompted variable to a
> report generates a Javascript "Object expected" error.
> Or is this still being researched? Anyone?
> Brian
>|||Finally, confirmation.
Thank you Brian.
"Brian Hartman [MSFT]" <brianhartman@.hotmail.com> wrote in message
news:ub8NqxMdEHA.3988@.tk2msftngp13.phx.gbl...
> We are aware of this. It is a bug. It happens when a parameter that you
> hide would normally have a null check box. If you can set the parameter
to
> non-nullable, that will fix the problem. Otherwise, there is no
workaround.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
> "G" <brian.grant@.si-intl-kc.com> wrote in message
> news:eJaxcCMdEHA.2752@.TK2MSFTNGP12.phx.gbl...
> > I'm just curious if Microsoft has officially recognized the bug in
Service
> > Pack 1, where attempting to pass a hidden and a prompted variable to a
> > report generates a Javascript "Object expected" error.
> >
> > Or is this still being researched? Anyone?
> >
> > Brian
> >
> >
>|||I have another symptom associated with hidden parameters to report:
Reporting Services does not respond when attempting to view a report that
has both "Prompted Credentials" AND hidden parameters. The only work-around
that I have found is to make all parameters visible (i.e. prompted) when
selecting prompted credentials for the data source.
M
"G" wrote:
> Finally, confirmation.
> Thank you Brian.
> "Brian Hartman [MSFT]" <brianhartman@.hotmail.com> wrote in message
> news:ub8NqxMdEHA.3988@.tk2msftngp13.phx.gbl...
> > We are aware of this. It is a bug. It happens when a parameter that you
> > hide would normally have a null check box. If you can set the parameter
> to
> > non-nullable, that will fix the problem. Otherwise, there is no
> workaround.
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no rights
> >
> > "G" <brian.grant@.si-intl-kc.com> wrote in message
> > news:eJaxcCMdEHA.2752@.TK2MSFTNGP12.phx.gbl...
> > > I'm just curious if Microsoft has officially recognized the bug in
> Service
> > > Pack 1, where attempting to pass a hidden and a prompted variable to a
> > > report generates a Javascript "Object expected" error.
> > >
> > > Or is this still being researched? Anyone?
> > >
> > > Brian
> > >
> > >
> >
> >
>
>

Pagebreak before Table and Expression on value Hidden

Hi Newsgroup,
in an Reporting-Services Report i have a table that is visible/hidden by a
specific parameter and it is set the pagebreak before table to true.
Now if the table is shown in the Report (The expression for the value hidden
returns false) the flag "Pagebreak before table" does not work.
If i remove the expression for the value hidden then the flag "Pagebreak
before table" works without any problems.
Seems to be a bug. Is there a fix or workaround for it?! Does SP1 for SQL
Server 2005 help for it?!
Best regards
DanielHi,
I have the same problem here. If anyone knows something please share
Best Regards,
Rui|||I had similar problems with page breaks not working when a table
visibility was being set by an expression using a report parameter
value (using RS2000 SP2). This appears to be a known issue - a quoted
Microsoft response on another forum states "Any conditional visibility
disables page breaks. We hope to make expression-based conditional
visibility (but not toggle-based conditional visibility) compatible
with page breaks in some future version".
I don't think this has been fixed in RS2005. I managed to implement a
(not ideal) work around by nesting tables inside rectangles and
applying the visibility expression to the rectangle, not the table. I
then applied page breaks to other items within the rectangle to
separate the page break attributes and the object visibility setting.
It doesn't work well with export to Excel though, since it affects
layout spacing and prevents separate pages being displayed on different
worksheets
Rui wrote:
> Hi,
> I have the same problem here. If anyone knows something please share
> Best Regards,
> Rui|||i have now the same problem on a ReportingServices 2005 Report.
I have placed the table in a rectangle. On the rectangle i have placed the
Visible/Hidden Expression. On the Table i have placed the page break before
setting.
Now in the report i get some blank pages. I work arround this report many
hours.
Is there no solution to use the pagebreak before and a visible/hidden
expression on one and the same table?!
The blankpages are on the export to pdf.
Thanks
Daniel
"AMasson" wrote:
> I had similar problems with page breaks not working when a table
> visibility was being set by an expression using a report parameter
> value (using RS2000 SP2). This appears to be a known issue - a quoted
> Microsoft response on another forum states "Any conditional visibility
> disables page breaks. We hope to make expression-based conditional
> visibility (but not toggle-based conditional visibility) compatible
> with page breaks in some future version".
> I don't think this has been fixed in RS2005. I managed to implement a
> (not ideal) work around by nesting tables inside rectangles and
> applying the visibility expression to the rectangle, not the table. I
> then applied page breaks to other items within the rectangle to
> separate the page break attributes and the object visibility setting.
> It doesn't work well with export to Excel though, since it affects
> layout spacing and prevents separate pages being displayed on different
> worksheets
> Rui wrote:
> > Hi,
> >
> > I have the same problem here. If anyone knows something please share
> >
> > Best Regards,
> > Rui
>