Pls Help me

MS team please help! I am running SRS SP1 (Version 8.00.878.00). I have a
report with this parameter in the Report Designer:
Name: DBName
Prompt: (blank)
Data Type: String
Allow Null Value: True
Allow blank Value: True
Available Values: Non-Queried (none)
Default Values: Non-Queried
value: dbname
I want to make this parameter hidden but expose it to the URL interface. So
I followed the SP1 instructions and published the report, then went to
Report Manager and checked the "Prompt User" checkbox then set the "Prompt
String" to blank.
This works fine. I can supply a parameter to the report via the URL, and the
user does not see the parameter to change its value.
However, then I add a second parameter to the report:
Name: Codes
Prompt: Codes:
Data Type: String
Allow Null Value: True
Allow blank Value: True
Available Values: Non-Queried (none)
Default Values: None
I deleted the report from the server in Report Manager, then published it
again from Visual Studio. I went back to Report Manager and again checked
the "Prompt User" and cleared the "Prompt String" for the parameter
"DBName". When I try to run the report and specify a value for the "DBName"
parameter on the URL I get the following error:
"A Runtime Error has occurred. Do you wish to debug?
Line: 80
Error: Object Required"
When I debug the error in MS Script Editor, it takes me to the following
code:
// Update the state of a nullable parameter.
function UpdateParam(nullChkBox)
{
// If the null checkbox itself is not enabled, don't change the state
// of the parameter controls. The null check box is disabled when
// a data driven parameter has outstanding dependencies
if (nullChkBox.disabled)
return;
It is failing on the if statement which means that nullChkBox is not an
object!!
I then tried going through all of the possible combinations of Default
Values, Allowing Null, etc. in the Report Manager for the "Codes" parameter.
The behaviour was consistent: If I check the "Prompt User" checkbox for the
"Codes" parameter at all then the report bombs! The same thing happens if I
change the order of hidden and prompted parameters. This would suggest that
there is a bug in SP1 handling reports containing a mix of hidden and
prompted parameters!!
I have seen this same script error reported in this news group on a July 2
article "Subject: Passing parameters via URL...", but I did not see a
satisfactory answer in Brian Welcker's (MSFT) reply as to why this error
message is appearing. It seems to me like a serious flaw in SQL Reporting
Services. Can anyone from the MS team help me with this one? As is often the
case, our implementation absolutely depends on this working!We used to have this same problem. I believe it has to do with page breaks
and is a bug solved in service pack 1. Down load this as soon as possible.
There are several great improvements and fixes in SP!.
"Raj Namachi" wrote:
> MS team please help! I am running SRS SP1 (Version 8.00.878.00). I have a
> report with this parameter in the Report Designer:
> Name: DBName
> Prompt: (blank)
> Data Type: String
> Allow Null Value: True
> Allow blank Value: True
> Available Values: Non-Queried (none)
> Default Values: Non-Queried
> value: dbname
>
> I want to make this parameter hidden but expose it to the URL interface. So
> I followed the SP1 instructions and published the report, then went to
> Report Manager and checked the "Prompt User" checkbox then set the "Prompt
> String" to blank.
> This works fine. I can supply a parameter to the report via the URL, and the
> user does not see the parameter to change its value.
> However, then I add a second parameter to the report:
> Name: Codes
> Prompt: Codes:
> Data Type: String
> Allow Null Value: True
> Allow blank Value: True
> Available Values: Non-Queried (none)
> Default Values: None
> I deleted the report from the server in Report Manager, then published it
> again from Visual Studio. I went back to Report Manager and again checked
> the "Prompt User" and cleared the "Prompt String" for the parameter
> "DBName". When I try to run the report and specify a value for the "DBName"
> parameter on the URL I get the following error:
> "A Runtime Error has occurred. Do you wish to debug?
> Line: 80
> Error: Object Required"
> When I debug the error in MS Script Editor, it takes me to the following
> code:
> // Update the state of a nullable parameter.
> function UpdateParam(nullChkBox)
> {
> // If the null checkbox itself is not enabled, don't change the state
> // of the parameter controls. The null check box is disabled when
> // a data driven parameter has outstanding dependencies
> if (nullChkBox.disabled)
> return;
> It is failing on the if statement which means that nullChkBox is not an
> object!!
> I then tried going through all of the possible combinations of Default
> Values, Allowing Null, etc. in the Report Manager for the "Codes" parameter.
> The behaviour was consistent: If I check the "Prompt User" checkbox for the
> "Codes" parameter at all then the report bombs! The same thing happens if I
> change the order of hidden and prompted parameters. This would suggest that
> there is a bug in SP1 handling reports containing a mix of hidden and
> prompted parameters!!
> I have seen this same script error reported in this news group on a July 2
> article "Subject: Passing parameters via URL...", but I did not see a
> satisfactory answer in Brian Welcker's (MSFT) reply as to why this error
> message is appearing. It seems to me like a serious flaw in SQL Reporting
> Services. Can anyone from the MS team help me with this one? As is often the
> case, our implementation absolutely depends on this working!
>|||Hi John Thanks for your help.I already installed service pack 1,still i am
facing the problem. :(
My problem is I have 10 parameters I like to show only 5 parameters in the
report but I like pass values to all parameters.when ever try to blank prompt
value i am getting javascript. if any one know work around pls let me know..
thanks
raj
"johnE" wrote:
> We used to have this same problem. I believe it has to do with page breaks
> and is a bug solved in service pack 1. Down load this as soon as possible.
> There are several great improvements and fixes in SP!.
> "Raj Namachi" wrote:
> > MS team please help! I am running SRS SP1 (Version 8.00.878.00). I have a
> > report with this parameter in the Report Designer:
> >
> > Name: DBName
> > Prompt: (blank)
> > Data Type: String
> > Allow Null Value: True
> > Allow blank Value: True
> > Available Values: Non-Queried (none)
> > Default Values: Non-Queried
> > value: dbname
> >
> >
> > I want to make this parameter hidden but expose it to the URL interface. So
> > I followed the SP1 instructions and published the report, then went to
> > Report Manager and checked the "Prompt User" checkbox then set the "Prompt
> > String" to blank.
> >
> > This works fine. I can supply a parameter to the report via the URL, and the
> > user does not see the parameter to change its value.
> >
> > However, then I add a second parameter to the report:
> >
> > Name: Codes
> > Prompt: Codes:
> > Data Type: String
> > Allow Null Value: True
> > Allow blank Value: True
> > Available Values: Non-Queried (none)
> > Default Values: None
> >
> > I deleted the report from the server in Report Manager, then published it
> > again from Visual Studio. I went back to Report Manager and again checked
> > the "Prompt User" and cleared the "Prompt String" for the parameter
> > "DBName". When I try to run the report and specify a value for the "DBName"
> > parameter on the URL I get the following error:
> >
> > "A Runtime Error has occurred. Do you wish to debug?
> > Line: 80
> > Error: Object Required"
> >
> > When I debug the error in MS Script Editor, it takes me to the following
> > code:
> >
> > // Update the state of a nullable parameter.
> > function UpdateParam(nullChkBox)
> > {
> > // If the null checkbox itself is not enabled, don't change the state
> > // of the parameter controls. The null check box is disabled when
> > // a data driven parameter has outstanding dependencies
> > if (nullChkBox.disabled)
> > return;
> >
> > It is failing on the if statement which means that nullChkBox is not an
> > object!!
> >
> > I then tried going through all of the possible combinations of Default
> > Values, Allowing Null, etc. in the Report Manager for the "Codes" parameter.
> > The behaviour was consistent: If I check the "Prompt User" checkbox for the
> > "Codes" parameter at all then the report bombs! The same thing happens if I
> > change the order of hidden and prompted parameters. This would suggest that
> > there is a bug in SP1 handling reports containing a mix of hidden and
> > prompted parameters!!
> >
> > I have seen this same script error reported in this news group on a July 2
> > article "Subject: Passing parameters via URL...", but I did not see a
> > satisfactory answer in Brian Welcker's (MSFT) reply as to why this error
> > message is appearing. It seems to me like a serious flaw in SQL Reporting
> > Services. Can anyone from the MS team help me with this one? As is often the
> > case, our implementation absolutely depends on this working!
> >|||The script bug is a known issue that is scheduled to be fixed in SP2. Do you
get the error if you actually specify a value for the Codes parameter?
--
Brian Welcker
Group Program Manager
Microsoft SQL Server
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Raj" <Raj@.discussions.microsoft.com> wrote in message
news:61398A3A-7376-413F-ABCA-99648F3A0989@.microsoft.com...
> Hi John Thanks for your help.I already installed service pack 1,still i am
> facing the problem. :(
> My problem is I have 10 parameters I like to show only 5 parameters in
> the
> report but I like pass values to all parameters.when ever try to blank
> prompt
> value i am getting javascript. if any one know work around pls let me
> know..
> thanks
> raj
> "johnE" wrote:
>> We used to have this same problem. I believe it has to do with page
>> breaks
>> and is a bug solved in service pack 1. Down load this as soon as
>> possible.
>> There are several great improvements and fixes in SP!.
>> "Raj Namachi" wrote:
>> > MS team please help! I am running SRS SP1 (Version 8.00.878.00). I have
>> > a
>> > report with this parameter in the Report Designer:
>> >
>> > Name: DBName
>> > Prompt: (blank)
>> > Data Type: String
>> > Allow Null Value: True
>> > Allow blank Value: True
>> > Available Values: Non-Queried (none)
>> > Default Values: Non-Queried
>> > value: dbname
>> >
>> >
>> > I want to make this parameter hidden but expose it to the URL
>> > interface. So
>> > I followed the SP1 instructions and published the report, then went to
>> > Report Manager and checked the "Prompt User" checkbox then set the
>> > "Prompt
>> > String" to blank.
>> >
>> > This works fine. I can supply a parameter to the report via the URL,
>> > and the
>> > user does not see the parameter to change its value.
>> >
>> > However, then I add a second parameter to the report:
>> >
>> > Name: Codes
>> > Prompt: Codes:
>> > Data Type: String
>> > Allow Null Value: True
>> > Allow blank Value: True
>> > Available Values: Non-Queried (none)
>> > Default Values: None
>> >
>> > I deleted the report from the server in Report Manager, then published
>> > it
>> > again from Visual Studio. I went back to Report Manager and again
>> > checked
>> > the "Prompt User" and cleared the "Prompt String" for the parameter
>> > "DBName". When I try to run the report and specify a value for the
>> > "DBName"
>> > parameter on the URL I get the following error:
>> >
>> > "A Runtime Error has occurred. Do you wish to debug?
>> > Line: 80
>> > Error: Object Required"
>> >
>> > When I debug the error in MS Script Editor, it takes me to the
>> > following
>> > code:
>> >
>> > // Update the state of a nullable parameter.
>> > function UpdateParam(nullChkBox)
>> > {
>> > // If the null checkbox itself is not enabled, don't change the state
>> > // of the parameter controls. The null check box is disabled when
>> > // a data driven parameter has outstanding dependencies
>> > if (nullChkBox.disabled)
>> > return;
>> >
>> > It is failing on the if statement which means that nullChkBox is not an
>> > object!!
>> >
>> > I then tried going through all of the possible combinations of Default
>> > Values, Allowing Null, etc. in the Report Manager for the "Codes"
>> > parameter.
>> > The behaviour was consistent: If I check the "Prompt User" checkbox for
>> > the
>> > "Codes" parameter at all then the report bombs! The same thing happens
>> > if I
>> > change the order of hidden and prompted parameters. This would suggest
>> > that
>> > there is a bug in SP1 handling reports containing a mix of hidden and
>> > prompted parameters!!
>> >
>> > I have seen this same script error reported in this news group on a
>> > July 2
>> > article "Subject: Passing parameters via URL...", but I did not see a
>> > satisfactory answer in Brian Welcker's (MSFT) reply as to why this
>> > error
>> > message is appearing. It seems to me like a serious flaw in SQL
>> > Reporting
>> > Services. Can anyone from the MS team help me with this one? As is
>> > often the
>> > case, our implementation absolutely depends on this working!
>> >