April 25, 2006 at 1:58 pm
Hi all,
I got the report working at one point, but I broke it later. I don't know where is the place I need to mend it.
I can run(with the !) the report from the Data tab. I see records come back. I can also build and deploy the report with no error. The stored procedure has been tested in sql query analyzer also. But when I open browser to run the report, strange things happened.
First, only one parameter showed asking for input - I should have 3 parameters. Then after I typed some value (although I did set a default value in the report) in the textbox. The error message " xxx is not parameter for procedure usp_xx_xx" came up.
I must have set the or unset the parameters somewhere so that it doesn't work now. I am passing 3 parameters to the report and the prompts have been hidden by editing the rdl file. In fact, if I run old stored procedure, the report still works fine except now prompt me one parameter for input. I got it work with no prompt before.
I hope I explain it clear enough, has anyone got this experience?
April 25, 2006 at 3:15 pm
Go to the Data Tab. using dropdown select the recordset your working with.
Then click the ... Elipse. Go to the parameters tab.
Make sure the report parameters are aligned with parameters there.
Sometimes adding parameters erases these values
April 26, 2006 at 1:12 pm
Hi,
Thank you very much for the reply. I gave up the hiding parameters task at the moment. I got the report to work to the point which shows the 3 parameters on the report. I need to make it disappear later so that the report gets it's parameters from URL.
Question 1 - What is the right way to hide the prompts? I have been deleting every chars between the prompt tags from RDL file. First of all, for some reason, there aren't any prompt tags in the DRL anymore. Secondly, I think this might not be the correct way to hide prompts. I had a feeling that it causes the error message " xxx is not a parameter for procedure xxx". I could be very wrong here, though.
Question 2 - a bigger one. When I preview the report from designer, I see more records than when I deploy it. The missing records are the ones that only part of the fields have values. In other words, these missing records have some null values in some fields. Does reporting services not handle the returned records well when the majority of the fields are null ?
Could someone point me to a direction, please?
Thank you for your help in advanced,
April 27, 2006 at 9:41 am
Hi all,
I think I got the second question solved. The reason is one of the missing value I have is located at the first column. I think it is this null value at the beginning of the metrix causing the missing records.
Thank you all anyway,
May 1, 2006 at 7:49 pm
from memory answer to question 1
You need to remove any prompt text from the parameter and ensure you supply a value to the parameter. This should stop the param displaying.
M
Martin
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply