WPF ReportViewer Issue

[Mark]

Hi,

We have upgraded to the Reporting Q3 2013 version which has broken our existing reports.

Here is an example of the XAML we are using: (RemitReport is the report property passed to the WPF View Window, type of Telerik.Reporting.Report)

    <telerik:ReportViewer x:Name="ReportViewer"
                              HorizontalAlignment="Stretch"
                              ReportSource="{Binding RemitReport, ElementName=thisWindow}" /> 

 When we try to run the report the following "Binding Error" appears in a window and our report view is empty.  However the control does render, just with no report displayed.

BindingExpression path error: 'NavigateBackCommand' property not found on 'object' ''RemitReportWindowViewModelProxy' (HashCode=37808243)'. BindingExpression:Path=NavigateBackCommand; DataItem='RemitReportWindowViewModelProxy' (HashCode=37808243); target element is 'RadButton' (Name=''); target property is 'Command' (type 'ICommand')

I've gone back and made sure all required references are present and are of the correct version.

 Any ideas what is happening?

Thanks.

[Stef]

Hello Mark,

Please check my post in the WPF: Binding ReportViewer.Report to Viewmodel property forum thread and verify the viewer's ReportSource property is bound to a model's ReportSource property.

Also check if both Telerik Reporting and Telerik UI for WPF are updated based on upgrade Path Q3 2013.

Regards,
Stef
Telerik

[Mark]

Thank you for your suggestions. I did review your post and it is of no help to us.  We have been down that path 2 or 3 times already with trying stuff to get this to work and have spent way, way too much time on this issue.

I have verified our code is returning a report so that is not the problem.  I have also verified all dependency references (Telerik.Windows.*) are version 2013.3.1016.40.  (I even put bindingRedirects in to make sure it was using the correct version)

Using the same XAML as my prior post (posted again)

   <telerik:ReportViewer x:Name="ReportViewer"
                              HorizontalAlignment="Stretch"
                              ReportSource="{Binding RemitReport, ElementName=thisWindow}" /> 

 Throws the same error everytime...

BindingExpression path error: 'NavigateBackCommand' property not found on 'object' ''RemitReportWindowViewModelProxy' (HashCode=37808243)'. BindingExpression:Path=NavigateBackCommand; DataItem='RemitReportWindowViewModelProxy' (HashCode=37808243); target element is 'RadButton' (Name=''); target property is 'Command' (type 'ICommand')

The ReportViewer is the only control on this form, so where is NavigateBackCommand and 'RadButton' coming from?. I have to assume at this point the error is being thrown by the ReportViewer and something to do with the toolbar associated with it.  I have tried every binding combination I have found on the Telerik site and nothing works.

This report is working in our current release of our product utilizing an old Telerik DLL version, but is now broken with the last Telerik update.

At this point, we have no choice to rip out a current working feature to get out the release.  I am out of ideas on why this is broken and how to fix it.  It all started with a Telerik update.

 

 

 

 

 

[Stef]

Hello Mark,

Such error can occur if Telerik UI for WPF assemblies or/and Telerik Reporting assemblies are not upgraded and there is loaded an old assembly. /Such error may appear if the viewer's ReportViewerModel is not bound properly to the viewer control, due to customization of the ReportViewerModel or due to the set current DataContext.

In order to provide you more accurate suggestions, we will need a demo project to check your settings.

Regards,
Stef
Telerik

[Mark]

OK. So if I understand what you are saying, we should do a FULL install of the newest release, not just update to the Reporting Q3 2013 references?

How would I go about getting this download?  My client already has an existing licensed Telerik version.  I know they are not going to pay for a new release just to fix this one issue since this had been working fine with an earlier release.

Thanks.

[Stef]

Hello Mark,

Products are synchronized on major releases, and upgrading Telerik Reporting requires upgrade of Telerik UI for WPF. If you use only Telerik Reporting, the product comes with a trial version of Telerik UI for WPF assemblies which get unlocked if used only by the ReportViewer in the application.

Regards,
Stef
Telerik

[Mark]

Thanks for your response, but I have no idea what you mean.  What exactly would we install?  All of our Telerik dll's are of the correct version along with any corresponding dll's for UI for WPF.  The client's application uses other Telerik controls that are installed, so if I'm reading your response correctly, this will not work as there is a possibility it will break other components of their system.

I appreciate your assistance, but at this point we have spent way too much time on something that was not in our control and we have to get this release out the door.  My advice to the dev team is to remove the Telerik controls and go to an alternative solution.  It is frustrating to have something working, upgrade, and have the feature break because of changes the third party made and has, what I feel, poorly documented and explained how to modify your code to work with the new version.

Again, I appreciate your assistance but it's time to move onto something that works instead of spinning our wheels for over 2 weeks with your new version trying every combination found on your sites to get this working.  Very, very frustrating.

 Thanks.

 

 

[Stef]

Hi Mark,

I am uncertain about the case and what requires you to upgrade only Telerik Reporting, but if it is a fix of an issue there is no way to provide the fix in an older versions, builds numbers are incremental.

Thus if you need to upgrade Telerik Reporting, it is a requirements to upgrade Telerik UI for WPF as well - applies when the old and the new versions are from different Q releases.

If you want to keep an old project with one version of Telerik Ui for WPF and upgrade only a module that uses Telerik Reporting, test to separate the module in its own project that can be started as a process from the main application. Thus the module can use different Telerik Ui for WPF version which is required by the dependencies of the WPF ReportVIewer.

The Manual Setup article elaborates on the requirements and the steps for adding and using the WPF ReportViewer.


On a side note, if it is an emergency please use the support ticketing system to describe the problem and send a demo project with the problematic settings. We try to monitor forums, but we cannot guarantee you a response by Telerik representative in a timely manner.

Regards,
Stef
Telerik