This is a migrated thread and some comments may be shown as answers.

Dependent Parameters not working

1 Answer 43 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
StevenDale
Top achievements
Rank 2
StevenDale asked on 02 Sep 2010, 05:09 AM

I am having trouble trying to use dependent parameters. I have the Reporting 2010 Q2. I have 8 images for the figure #'s described below.

1. I have SQLDatasource, using a stored proc, called Providers that gets a list of Providers. This stored proc returns Name and Id fields. Figure 1.

2. I have a ReportParameter called Provider that uses the Providers Data Source for its DataSource. Name is the DisplayMember and Id is the ValueMember. That works and displays correctly in Preview Mode in the designer and on the Report Viewer.

3. I have a second SQLDatasource, using a stored proc, called ProviderClasses that gets a list of Classes for the selected Provider. The stored proc returns Name and Id fields. This stored proc takes a parameter. Figure 3. The parameter is set to the Parameters.Provider.Value.Figure 4.

4. I have a ReportParameter called ProviderClass that uses the Classes Data Source for its DataSource. ClassName is the DisplayMember and Id is the ValueMember. Figure 5. This displays an error message and shows no values when I change the Providers dropdown. Figure 6.

If I open SQL Profiler and I select a provider, it does call the stored procedure with the Id of the selected Provider to populate the classes. When I run this exec command copied out of Profiler in a query window it returns the classes as expected. However, they don't populate the Class dropdown list on the Report Viewer. Figures 7 & 8.

I followed the examples even though they were using SQL text and not stored procedures.

What am I doing wrong?

Thanks,

BIlly Jacobs

1 Answer, 1 is accepted

Sort by
0
Steve
Telerik team
answered on 03 Sep 2010, 05:15 PM
Hello Billy,

I'm sorry to say but we were not able to reproduce such a problem on our end. One thing that comes to mind is whether you're using temp tables in your stored procedures. If this is the case, please review the following forum post for more information on the issue encountered.
If this is not your scenario and the problem persists, please open a support ticket and attach a sample runnable project showing the problem.

Regards,
Steve
the Telerik team
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 Public Issue Tracking system and vote to affect the priority of the items
Tags
General Discussions
Asked by
StevenDale
Top achievements
Rank 2
Answers by
Steve
Telerik team
Share this question
or