Hi
After upgrading my reports to the latest version Im having problems selecting my dataset as datasource in the report designer.
When I select DataSource in the property viewer, my old DataSets are not there.
However, when try to show all datasource in my project (using the VS 2010 menu "Data/Show Data Sources") they are all there.
So, why can't I see the datasets in the report designer select datasource windows, when I can see them in the "Data/Show Data Sources" window ?
When I try to add a new datasource to my report, I can only select "SQL DataSource" or "Object DataSource".
Is its still possible to use a DataSet as datasource in the Q1 release?
Regards
Per
After upgrading my reports to the latest version Im having problems selecting my dataset as datasource in the report designer.
When I select DataSource in the property viewer, my old DataSets are not there.
However, when try to show all datasource in my project (using the VS 2010 menu "Data/Show Data Sources") they are all there.
So, why can't I see the datasets in the report designer select datasource windows, when I can see them in the "Data/Show Data Sources" window ?
When I try to add a new datasource to my report, I can only select "SQL DataSource" or "Object DataSource".
Is its still possible to use a DataSet as datasource in the Q1 release?
Regards
Per
5 Answers, 1 is accepted
0
Hello Per,
Since Q1 2010 DataSet is no more the preferred type of data source object. Instead we have introduced the new Data Source Components and this is the suggested way to proceed from now on. You can still use DataSet as a data source but you should create it by yourself. As you have correctly noticed the ObjectDataSource is the way to go.
Anyway if your reports display data from a database, instead of using DataSets and DataTables we suggest using the SqlDataSource component that is designed to work especially with Telerik's reporting engine thus offering much better performance.
Sincerely yours,
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.
Since Q1 2010 DataSet is no more the preferred type of data source object. Instead we have introduced the new Data Source Components and this is the suggested way to proceed from now on. You can still use DataSet as a data source but you should create it by yourself. As you have correctly noticed the ObjectDataSource is the way to go.
Anyway if your reports display data from a database, instead of using DataSets and DataTables we suggest using the SqlDataSource component that is designed to work especially with Telerik's reporting engine thus offering much better performance.
Sincerely yours,
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.
0
Gersh
Top achievements
Rank 2
Rank 2
answered on 02 Nov 2011, 10:10 PM
Hi I had a question that relates to this topic.
I have a dataset with three datatables, but no relationships are distinguished by any of these 3 datatables. The fourth table is a mapping table, able to correlate what I want my report to show. This mapping table only has the ids of the other 3 datatables to use as references (IE groups datatable correlates to groups_id in the mapping table). My question is, can this mapping be done using objectDataSource, or do I have to map the tables to create a bigger datasource?
I have a dataset with three datatables, but no relationships are distinguished by any of these 3 datatables. The fourth table is a mapping table, able to correlate what I want my report to show. This mapping table only has the ids of the other 3 datatables to use as references (IE groups datatable correlates to groups_id in the mapping table). My question is, can this mapping be done using objectDataSource, or do I have to map the tables to create a bigger datasource?
0
Massimiliano Bassili
Top achievements
Rank 1
Rank 1
answered on 03 Nov 2011, 09:47 AM
You would have to flatten the tables into one if they do not have any relation.
0
Rafa
Top achievements
Rank 1
Rank 1
answered on 16 Oct 2014, 09:29 AM
Hi Steve,
I know this forum is old, but I just curious why Data Source is recommended instead of DataSet. In my project, the DataSet's Connection String will have different value, depends on the user. Using DataSet, it can be handled easily where I only change (Programmatically) One DataSet's Connection String since my whole reports source is bind to that DataSet. However, when using Data Source, each report can only use its own Data Source (as far as I know). So say if I have 30 reports, I will have 30 Data Sources, in which i need to change each of their Connection Strings. Is there any recommended way to handle this? Please advice.
Thank You.
Regards,
Rafa
I know this forum is old, but I just curious why Data Source is recommended instead of DataSet. In my project, the DataSet's Connection String will have different value, depends on the user. Using DataSet, it can be handled easily where I only change (Programmatically) One DataSet's Connection String since my whole reports source is bind to that DataSet. However, when using Data Source, each report can only use its own Data Source (as far as I know). So say if I have 30 reports, I will have 30 Data Sources, in which i need to change each of their Connection Strings. Is there any recommended way to handle this? Please advice.
Thank You.
Regards,
Rafa
0
Rafa
Top achievements
Rank 1
Rank 1
answered on 17 Oct 2014, 08:36 AM
Hi,
I solve my problem by referring to this post : Changing the connection string dynamically according to runtime data. Thank you very much for this!
Regards,
Rafa
I solve my problem by referring to this post : Changing the connection string dynamically according to runtime data. Thank you very much for this!
Regards,
Rafa