What's New in Telerik Reporting Q3 2010 (v4.2.10.1110)
- Added a new data source component:
- Added native (Silverlight 4) printing in Silverlight Report Viewer.
- Added new interactive action
- ToggleVisibilityAction (drill down)
- Added XML serialization on report definition. See video.
What's Fixed
Visual Studio Report Designer
- Fixed: An error occurs when Report Wizard/Table Wizard is about to display the data fields of a complex object data source
Data Sources\SqlDataSource
- Improved: SqlDataSource now offers generic database support
WCF Report Service
- Fixed: An error occurs when using WCF Report Service with out-proc session state mode
Silverlight Report Viewer
- Silverlight Report Viewer is now build against Silverlight 4 and RadControls for Silverlight Q3 2010
Report Viewer for ASP.NET
- Fixed: Loading image is prematurely hidden when the parameters area loads
Breaking Changes
- CHANGE: Telerik.Reporting.Group.Grouping property is now OBSOLETE. Use Telerik.Reporting.Group.Groupings property instead.
- CHANGE: Telerik.Reporting.TableGroup.Grouping property is now OBSOLETE. Use Telerik.Reporting.TableGroup.Groupings property instead.
- CHANGE: Telerik.Reporting.Group.Sorting property is now OBSOLETE. Use Telerik.Reporting.Group.Sortings property instead.
- CHANGE: Telerik.Reporting.TableGroup.Sorting property is now OBSOLETE. Use Telerik.Reporting.TableGroup.Sortings property instead.
- CHANGE: Telerik.Reporting.Report.Sorting property is now OBSOLETE. Use Telerik.Reporting.Report.Sortings property instead.
- CHANGE: Telerik.Reporting.Table.Sorting property is now OBSOLETE. Use Telerik.Reporting.Table.Sortings property instead.
- CHANGE: Telerik.Reporting.Chart.Sorting property is now OBSOLETE. Use Telerik.Reporting.Chart.Sortings property instead.
- CHANGE: Telerik.Reporting.ReportParameterAvailableValues.Sorting property is now OBSOLETE. Use Telerik.Reporting.ReportParameterAvailableValues.Sortings property instead.
- CHANGE: SqlDataSource against the Oracle data provider now expects the parameter names without the leading colon ( : ) character, which is the correct behavior according to the specification. For existing reports the leading colon ( : ) character should be removed from the parameter names. Running the SqlDataSource wizard can also fix the obsolete parameter names.