July 24, 2008 at 10:46 am
Hi,
I have several reports that have been working fine in Reporting Services until a problem was uncovered recently. One of the prompts that is required in order to run the report brings back too many values. So we put in a search text box for the user to enter search criteria. When the user hits the tab button or clicks the mouse somewhere in the window or hits the enter key a Stored Procedure is run and brings back a subset of the values for the prompt. The problem is if after putting in the search criteria the user clicks on "View Report" the prompt with the subset of values is not filled, the user is not prompted for the missing parameter values and the user gets an error message rather than the report. All other prompts work correctly in that the user is prompted for a missing parameter value when missing. Does anyone have any idea why this one prompt does not work correctly?
Any help with this problem would be greatly appreciated! Thanks.
July 25, 2008 at 4:52 am
I might be over simplifying this but have you tried setting the parameter to not allow Nulls or Blanks?
Nigel West
UK
July 25, 2008 at 5:54 am
Hi Nigel,
I have verified that those are both not checked. I also removed the default value criteria and it did not fix the problem. This only happens when running on Reporting Services, it runs ok in VS 2005.
Thanks for your response, any other ideas would be greatly appreciated!
Steve
July 25, 2008 at 6:14 am
Can you tell me if this is a standard SSRS Parameter, it appears when you use the word TextBox that you have somehow created an input box on the report itself.
If this is a standard SSRS Parameter, what is the Stored Procedure doing? Is the SP used to provide a list of values for selection from that parameter (i.e. the SP creates a drop down list).
What is the connection between that parameter and other parameters in the report.
Regards,
Nigel West
UK
July 25, 2008 at 7:09 am
Hi Nigel,
It is a standard SSRS parameter in that it is created in the Report Parameters popup box within VS. What I meant when I said it is a "text box" is that it has no available values or default values. The parameter, Supplier Search, triggers a stored procedure that will bring back a subset of supplier names based on what the user inputs into the search parameter which are then populated in the Supplier drop down parameter. In order to trigger the SP the user needs to hit the tab button, click the mouse somewhere in the webpage or hit the Enter key. The problem is encountered if the user hits the View Report button instead. The Supplier drop down parameter does not get populated from the SP and the validation on that parameter is not triggered to let the user know that a Supplier needs to be chosen. Instead you get the following error mesage:
There is an error in XML document (1, 158286).
'', hexadecimal value 0x1A, is an invalid character. Line 1, position 158286.
Does this give you a better idea of how things work for this report? Again I appreciate all your help that you are giving me here, and let me know if I need to explain any part of this better.
Steve
July 25, 2008 at 7:34 am
OK, so now I think I am clear on what you are trying to do, and I assume that the supplier drop down parameter is used in your final dataset query to return the data for one/many/all suppliers selected in this parameter (i.e. you send that final parameter into the stored procedure for the report dataset).
So the question then would be, does the final supplier select parameter have a default value? If it does then remove it, make the default null.
If you hit the view report button it should not allow you to move forward unless the final parameter is completed. However, some people will not use the parameter value in the dataset, they might use it to change the visibility of rows/cells in a table. In this case the report will carry on without you having to complete the parameter, but even then it shouldn't give you an error.
I'm struggling to know what is causing the problem.
Nigel West
UK
July 25, 2008 at 7:42 am
You are correct that the selected values in the Supplier parameter are then used in the SP that brings back the report values. I already tried removing the default values for Supplier and also removed the report and then redeployed the report to the Reporting Services site. We are still getting the erroneous processing.
This is turning into a really difficult error to debug. :sick:
July 25, 2008 at 7:52 am
Sorry, struggling now, will have a think about it and maybe put an example together to see if I can reproduce it.
Nigel West
UK
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply