I hope you enjoyed the webinar on the Q2 2013 release of Telerik Reporting and OpenAccess ORM. There were plenty of exciting things to share and some really great questions from the attendees.
As promised, we have made available the recording as well as the slides for your viewing pleasure.
In this webinar we covered some exciting new features of Telerik Reporting.
The ability to make graphs interactive has been added to the toolset. This means you have the ability to add actions to category groups that have the ability to expand and collapse parent-child relationships across the same axis, on top of the ability to trigger any other action such as the opening of a subreport, toggle visibility of a report item, link to a webpage or even jump to another location within the same report. Our demo even demonstrated how the graph wizard was able to automatically detect the parent-child relationship from our data source and build the expand and collapse functionality automatically.
Next we demonstrated the new properties that allow you to have more control over how your polar graphs are rendered. Two properties were added to the PolarCoordinateSystem class that allow you to set a starting angle for your graph rendering (AngularAxisStartAngle) and also set the sweep angle (AngularAxisSweepAngle). In our demonstration we showed how to render a half-circle doughnut graph, though this functionality is available on all polar graphs including pie, and all the radar graphs.
The last thing we covered for Telerik Reporting for the Q was that Telerik Reporting is now being built on .Net 4.0. This allows you to use all the enhancements in the .Net framework since .Net 2.0 in any of your custom code written for reports. With this update, only Visual Studio 2010 and Visual Studio 2012 are supported. You will not be forced to upgrade your .Net 2.0 or .Net 3.0 Telerik Reporting projects unless of course you wish to use new and upcoming features of Telerik Reporting going forward. Technical support for existing .Net 2.0 and .Net 3.0 Reporting projects will continue for one calendar year, expiring in June 2014.
Q: Does the Wizard automatically detect the relationship between fields dragged to the category group
A: Yes, the Wizard can detect parent-child relationships and will automatically create the expand and collapse functionality that you saw in the demo.
Q: Is there 3D capabilities in the Graph control?
A: Not currently, though you can submit your ideas to the feedback portal at http://www.telerik.com/feedback
Q: What converters exist to convert existing reports to Telerik Reports?
A: The Report Converter Wizard will convert Crystal Reports, XtraReports and ActiveReports to Telerik Reports
Q: Can Reports use OData as a data source ?
A: Yes definitely – you can find more information in this blog post.
Q: Can Telerik Reporting handle complex queries?
A: Yes, any query that you can run directly against the database can be used with Telerik Reporting. Though you are limited by the performance of the database and the network depending on the number of rows being returned. In designing your reports, you should follow this guidance from our documentation.
Q: Can Telerik Reporting export to xls or csv ?
A: Yes, both of those file types are supported export types in Telerik Reporting
Q: How do you deploy Telerik Reports ?
A: If you create the report in Visual Studio, typically reports are deployed as part of a DLL, if you wish to deploy from Report designer you can follow the following guidance.
Q: Can I bind to a DataTable in Telerik Reporting?
A: Yes, Telerik Reporting supports all ADO.Net based data sources including DataTables, you can find more information in the documentation.
Three features highlighted of this Q’s webinar for OpenAccess ORM.
We improved the Update Database from Model command to allow you to drop tables created by no-longer used domain objects. Using the Fluent API, you have even finer-grained control by dropping items like foreign keys.
The brand new Bulk Update and Delete uses a LINQ-style syntax with the Context API. You don’t need to retrieve the entities before performing these operations, and you don’t need to write SQL. The operations execute only one SQL command, and as far as I am aware, OpenAccess is the only .NET ORM that allows this. Others retrieve the entities behind the scenes, resulting in many query executions.
Finally, we have new code generation options, enabled by our newly refactored T4 templates. We’ve added four, and we created a GitHub project so you can grab other code generations.
Q: The migration is supported also in code? I'm thinking of a couple of project when I'll have to use SQLite dbs, and I'd like to support schema/data migration from version to version
A: Yes, it is. You can do it using the code-only Fluent API (a simple .Drop() method call, declaratively), and during runtime you can update your database schema - including addint/removing tables, columns, indexes or constraints.
Q: Is OpenORM open source and if not are there any plans for that scenario?
A: For the time being we do not have plans to make OpenAccess ORM open source. However, we do provide huge portions of the source code for DevCraft license holders.
Q: Is there a level 2 caching built in?
A: Yes, level 2 caching is an option in OpenAccess ORM - you can work with or without it, depending on your preference.
Q: Is there any comparison chart with Entity Framework ?
A: Yes, take a look here: http://www.telerik.com/products/orm/getting-started/openaccess-vs-entity-framework.aspx . For any specific questions, just post them in the forums and we will explain what you can do with OpenAccess ORM.
We hope that you enjoyed learning about what is new in Telerik Reporting and OpenAccess ORM. Feel free to reach out to us at any time through email, twitter or the feedback portal.
Carey Payette is a Developer Advocate. You can follow Carey on Twitter @careypayette or read her personal blog at www.codingbandit.com.
Copyright © 2017, Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.