Errors after upgrading to Q1 2013

[Dan]

I have just upgraded to Q1 2013 of Reporting and I have lots of errors in the .Designer.cs files such as:

formattingRule1.Filters.AddRange(new Telerik.Reporting.Data.Filter[] {new Telerik.Reporting.Data.Filter("RowNumber()%2", Telerik.Reporting.Data.FilterOperator.Equal, "=1")});

The best overloaded method match for 'Telerik.Reporting.FilterCollection.AddRange (System.Collections.Generic.IEnumerable<Telerik.Reporting.Filter>)' has some invalid arguments
-------
Argument 1: cannot convert from 'Filter[]' to 'System.Collections.Generic.IEnumerable<Telerik.Reporting.Filter>'
-------
The type or namespace name 'Filter' does not exist in the namespace 'Telerik.Reporting.Data' (are you missing an assembly reference?)

Am I missing a dll reference?

Dan

[Michael]

I've a feeling its all moved to just telerik.reporting (remove the .filters)?  but i aint no expert

[Peter]

Hello Dan,

In Q1 2013 we have removed the obsolete properties in question. Generally changed API in the designer is best handled manually by opening a report in the report designer and making a small change e.g. turn on/off the report snap grid, move a textbox a little etc and the report would be serialized with the new proper API without any need for manual intervention. However this will only work for types that are obsolete and not yet removed. Thus our suggestion is to downgrade to a previous official release for example Q3 2012 SP1 , for the downgrade process you can still use the upgrade wizard. After the successful downgrade and project build you have to update the obsolete code as instructed and then you can successfully upgrade to Telerik Reporting Q1 2013 release.

Generally prior removing any types or properties we keep them obsolete for several Qs. Thus our suggestion is after an upgrade to check the project build warning and to handle any obsolete code warnings.

All the best,
Peter
the Telerik team

[Dan]

Wow!

[Dan]

I did the downgrade, compile, upgrade.  That fixed it.  Thanks!

Dan

[Mark]

I'd like to add to this particular thread as I am having the same issue.  I'm trying to revive a prototype and have managed to get up to release Q1 2012 (6.0.12.215).  When I build the report project, there are no warnings that any of the pending obsolete properties, yet at Q1 2013 I am presented with a few hundred errors based on issues such as: 'Telerik.Reporting.GroupingCollection.AddRange(System.Collections.Generic.IEnumerable<Telerik.Reporting.Grouping>)'

The point is, the upgrade wizard and build advisements may not be nearly as forgiving or informative as you posit.

In my specific situation I have to try to find an interim distribution to see if I can mitigate the changes.  This becomes a challenge as (at least to my knowledge) Telerik does not make previous versions readily available.

[Squall]

@Mark

Have you tried as Peter said to upgrade first to Q3 2012 SP1 and then to Q1 2013?

[James]

I have run into the same issue with this, except that cannot download the 2012 version. All I have available is 2 different 2013 builds.

[Mark]

@Squall It would seem you missed my point.  Unfortunately all releases are not always readily available so while the process itself may be straight forward, the bits may not be accessible.

To Telerik's credit, however, they seem to try and be accommodating when it is reasonable and they are able - even in unusual circumstances. 

[James]

@James

Use this page to download older releases.

[James]

I was able to get in touch with tech support and they were able to get the older version on my available downloads.

I am still having some trouble using a ReportBook. The migration page doesn't cover this topic.

http://www.telerik.com/support/kb/reporting/general/q2-2012-api-changes-reportsources.aspx#reportprocessor

[James]

After a few minutes more fiddling around I figured it out.

You can set a report book as an ReportInstanceSource.

Which resolves all the issues I've run into with this.