Brian Mains
Top achievements
Rank 1
Rank 1
Brian Mains
asked on 18 Jan 2010, 09:53 PM
Hello,
I'm using this approach to bind a form: http://blogs.telerik.com/kevinbabcock/posts/09-03-14/telerik_reporting_connecting_to_stored_procedures.aspx
So I'm using a stored proc, and binding the data in the needdatasource event. I have four parameters, but I see no parameter list to be able to edit them... what is going on, do I need to enable something? I'm at a loss here as to how I can supply property values in the ASPX web page and in the preview window.
Note, I setup the parameters in the properties grid in the designer.
Thanks.
I'm using this approach to bind a form: http://blogs.telerik.com/kevinbabcock/posts/09-03-14/telerik_reporting_connecting_to_stored_procedures.aspx
So I'm using a stored proc, and binding the data in the needdatasource event. I have four parameters, but I see no parameter list to be able to edit them... what is going on, do I need to enable something? I'm at a loss here as to how I can supply property values in the ASPX web page and in the preview window.
Note, I setup the parameters in the properties grid in the designer.
Thanks.
2 Answers, 1 is accepted
0
Brian Mains
Top achievements
Rank 1
Rank 1
answered on 18 Jan 2010, 10:29 PM
OK, figured that out, but noticed a bug. All of my parameters defaulted to visible="false"? IMO, they should be set to true. Also, when I used the group designer, I went back into my properties and they got reset to false... potential bug?
0
Hello Brian,
The report parameters are indeed Visible=false and this is by design. They are setup this way so that the built-in parameters area is not shown if not needed (it is not customizable and provides basic out of the box handling only) and you can still pass values to the params from your actual app i.e. introduce your own UI.
As for your second report - we were not able to reproduce such an issue. The Visible property of the parameters is serialized properly and had not changed after playing with the groups. If you can replicate this steadily, please provide us with steps to do so.
Kind regards,
Steve
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
The report parameters are indeed Visible=false and this is by design. They are setup this way so that the built-in parameters area is not shown if not needed (it is not customizable and provides basic out of the box handling only) and you can still pass values to the params from your actual app i.e. introduce your own UI.
As for your second report - we were not able to reproduce such an issue. The Visible property of the parameters is serialized properly and had not changed after playing with the groups. If you can replicate this steadily, please provide us with steps to do so.
Kind regards,
Steve
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.