i need to create a report which has a couple of drop downs as parameter(filters). each drop down is populated through calling a stored procedure.
my problem is that when i create a dataset and bind it to my drop down and when i add those drop downs to my telerik report, the drop downs won't be populated. do you know why?
is this doable at all using telerik report to have dynamic drop down parameters?
15 Answers, 1 is accepted
The described scenario is supported and the provided information is not sufficient to pinpoint the root of the issue. Thus we will appreciate if you elaborate further on your scenario and send us a sample runnable report to review and debug on our end.
Generally you may find useful the report parameters videos at tv.telerik.com and the report parameters help articles.
the Telerik team
The SQL Datasource is correct because I can create a report and display the data but when the parameter is attached to the datasource we get NOTHING.
I figured out your problem. The parameter list you are building is using a Guid for the value portion of the drop-down parameter. Guids are not supported so we need to convert the value to string before it will display the options to select from.
It would be great if the Report parameters could allow Guids/Uniqueidentifiers. Or at least give an error to inform the developer of the problem. :)
Check the How to use a Guid as value for report parameter or data source parameter? KB article for more information.
the Telerik team
The KB article can be found here: How to use a Guid as value for report parameter or data source parameter?
Not happened much (anything) up to now. Still not working with Guids and no helpful information/error display.
Need to convert the Guid to string for report filters (ValueMember) and then if you want to pass the report parameter/filter preselection you have to take attention to the character case which differs from .NET and SQL data source!
BTW: I use ToString() and don't know what are the (dis) advantages compared to CStr()
One more approach I can suggest you is to convert to strings GUID values on data-retrieval (in data). Thus you will not have to care about the conversion in expressions and the report.
Feel free to add a feature request for having support for GUID or other type of report parameters. Features are considered for implementation based on the demand for them.
I'm not quite sure if I understand you correct.
I also tried casting the GUID/Uniqueidentifier to string in the SQL query for the report filter values instead of using the .NET framework ToString function in the ValueMember assignment. But then the filter preselection with the externally passed report parameter didn't work anymore because SQL server converts Uniqueidentifier to an uppercase string whilest the externally passed GUID converted from the .NET framework is a lowercase string.
This is one of the main issues. The other one is that if you're using guids instead of strings for the filter values it doesn't work anymore or the filter values won't even display anything. No error message either.
But this issues are only related with filtering (visible=true). when just using as "normal" report parameter I never expirienced any issues and never did any manual conversions.
You can convert GUIDs to strings in the data-retrieval method. If you need to control the data on retrieval, you can use a string report parameter which is compared to the converted in string GUID.
If there are issues with the string case, you can use the built-in ToLower and ToUpper functions in reports and the corresponding in the data-retrieval method (e.g. TSQL UPPER string function).
If you need further help, please post an example illustrating the problem, and description how to reproduce the problem.
I have a problema, on my SQL Database I have an uniqueidentifier field, with data as 85866F4D-BAFC-428B-A998-75757247779C, but when I report it on my telerik report, appears as 85866f4d-bafc-428b-a998-75757247779c!! Why??? it is wrong, I need to it appears as is it in the Database
As Stef mentioned, you can choose one of the following approaches to display GUIDs to uppercase. But first you'll need to convert the GUIDs to strings in the data-retrieval method and then:
- using ToLower and ToUpper functions in reports;
- or TSQL UPPER string function in the data-retrieval method.
Ok, thank you, it Works: ToUpper(CStr(Fields.UUIDPago))