Telerik Report with Drop down parameters

13 posts, 0 answers
  1. Zahra Mottaghi-Far
    Zahra Mottaghi-Far avatar
    7 posts
    Member since:
    Sep 2009

    Posted 06 Jan 2010 Link to this post

    hi ,

    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?

    thanks
    zahra
  2. Michael Barbu
    Michael Barbu avatar
    12 posts
    Member since:
    Feb 2010

    Posted 19 Oct 2011 Link to this post

    I'm having the same problem. Did you happen to find a solution?
  3. DevCraft banner
  4. Peter
    Admin
    Peter avatar
    1611 posts

    Posted 24 Oct 2011 Link to this post

    Hi Michael Barbu,

    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.

    Regards,
    Peter
    the Telerik team

    Q2’11 SP1 of Telerik Reporting is available for download (see what's new). Get it today.

  5. Brad
    Brad avatar
    1 posts
    Member since:
    Sep 2011

    Posted 24 Oct 2011 Link to this post

    I'm attaching a sample of the code that I still can't get to work.
    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.
  6. Ryan
    Ryan avatar
    11 posts
    Member since:
    Aug 2008

    Posted 25 Oct 2011 Link to this post

    Michael Barbu,

    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.


    Peter,

    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. :)
  7. Michael Barbu
    Michael Barbu avatar
    12 posts
    Member since:
    Feb 2010

    Posted 25 Oct 2011 Link to this post

    I agree, it is silly that you can not use a Guid.
  8. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 25 Oct 2011 Link to this post

    Hi Michael,

    Check the How to use a Guid as value for report parameter or data source parameter? KB article for more information.

    Kind regards,
    Steve
    the Telerik team

    Q2’11 SP1 of Telerik Reporting is available for download (see what's new). Get it today.

  9. Martin
    Martin avatar
    19 posts
    Member since:
    Feb 2012

    Posted 06 Feb 2014 in reply to Steve Link to this post

    Broken Link
  10. Stef
    Admin
    Stef avatar
    3041 posts

    Posted 10 Feb 2014 Link to this post

    Hi Martin,

    The KB article can be found here: How to use a Guid as value for report parameter or data source parameter?

    Regards,
    Stef
    Telerik

    New HTML5/JS REPORT VIEWER with MOBILE AND TOUCH SUPPORT available in Telerik Reporting Q3 2013! Get the new Reporting version from your account or download a trial.

  11. Fridli Jacober
    Fridli Jacober avatar
    89 posts
    Member since:
    Dec 2009

    Posted 30 Sep 2015 Link to this post

    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()

  12. Stef
    Admin
    Stef avatar
    3041 posts

    Posted 02 Oct 2015 Link to this post

    Hi Fridli,

    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.

    Regards,
    Stef
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  13. Fridli Jacober
    Fridli Jacober avatar
    89 posts
    Member since:
    Dec 2009

    Posted 05 Oct 2015 in reply to Stef Link to this post

    Hi Stef

    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.

  14. Stef
    Admin
    Stef avatar
    3041 posts

    Posted 07 Oct 2015 Link to this post

    Hello Fridli,

    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.

    Regards,
    Stef
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Back to Top
DevCraft banner