While working in the standalone Report Designer (Q2 2014), I encountered an issue while trying to set up a datasource for a new band report. What I'm trying to do is set up a SQL stored procedure as a data source. I'm able to select my normal connection string, and I'm able to select my stored procedure from the dropdown list and run a successful test query against it. The problem is that after I exit the wizard the Data Explorer Window does not show my data source or any data fields associated with it; as if there was no data source. So far I've tried setting it up from the wizard dialogue that appears when setting up a new report, as well as from the properties window of an unconfigured data source. (I've attached an image showing what the screen looks like after trying to set it up)
Has anyone else run into this? If so, does it only trigger for certain types of stored procedure? (I ask because this has only happened for one of my stored procedures so far.)
Report Designer Version: 8.1.14.804
OS: Windows 7 Professional (64-bit)
Has anyone else run into this? If so, does it only trigger for certain types of stored procedure? (I ask because this has only happened for one of my stored procedures so far.)
Report Designer Version: 8.1.14.804
OS: Windows 7 Professional (64-bit)
1 Answer, 1 is accepted
0
Hi Jacob,
Do you have temp tables in the stored procedure? Generally there is a temp tables problem due to Microsoft's bug with reading the Metadata. You can find more information on this subject and suggested solution in the following forum thread: Temporary Table in Stored Proc.
Additionally make sure that you have set a valid design time parameter value according to the stored procedure requirements. Specifying design time values for the parameters is necessary because the designer might need to execute the SQL query or stored procedure of the data source in order to populate the schema displayed in the Data Explorer tool window and the Edit Expression dialog. These values do not affect the execution of the SQL query at runtime however.
Regards,
Peter
Telerik
Do you have temp tables in the stored procedure? Generally there is a temp tables problem due to Microsoft's bug with reading the Metadata. You can find more information on this subject and suggested solution in the following forum thread: Temporary Table in Stored Proc.
Additionally make sure that you have set a valid design time parameter value according to the stored procedure requirements. Specifying design time values for the parameters is necessary because the designer might need to execute the SQL query or stored procedure of the data source in order to populate the schema displayed in the Data Explorer tool window and the Edit Expression dialog. These values do not affect the execution of the SQL query at runtime however.
Regards,
Peter
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.