This is a migrated thread and some comments may be shown as answers.

Evaluating Report tool for WPF

9 Answers 84 Views

General Discussions

This is a migrated thread and some comments may be shown as answers.

Cedric asked on 29 Jan 2019, 02:12 PM

programme_blé_tendre_hiver.png

programme_vigne.png

timeline_culture_perenne.png

Hello,

I'm in charge to evaluate the component Report tool for wpf for an integration in our product.

I'm confident to produce standard reporting elements but in the reports we want to edit, we should be able to reproduce a grid like the ones attached in this post.

Is it easily possible with your component ? I don't want to have to draw a grid line by line as it will be necessary with raw pdf technology.

Regards,

Cédric

9 Answers, 1 is accepted

answered on 01 Feb 2019, 11:18 AM

Hi Cédric,

The general layout of the reports as seen from the screenshots is easily achievable with Crosstab item. In the table cells you may place PictureBoxes, TextBoxes, Panel (i.e. container for more report items) or other nested data items (e.g. Graph, other Table), etc. In the Crosstab there is row grouping and column grouping by default to dynamically generate row/columns in the table based on the received data. Table cells may also be merged.
In one of the screenshots, I noticed merging of only some of the table cells. Generally, table cells can be merged in the report definition. In some conditions, it may be possible to merge cells also based on the incoming data. Bindings and Conditional Formatting may be very useful in this case.

We provide out of the box a WPF Report Viewer for displaying our reports in a WPF application.

The best way to evaluate our product will be to download our fully functional Trial version. It comes with free Support for the period of evaluation so we would be able to help and guide you.

Regards,
Todor
Progress Telerik

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 Feedback Portal and vote to affect the priority of the items

answered on 04 Feb 2019, 01:31 PM

I will post my question in this thread to not pollute the forums with all my problems.

First, the wpf component reportviewer is not enabled in my solution :(
During the installation of the trial, i first unchecked the 'visual studio integration' because in general i prefer to keep my visual studio installation as light as possible, but may be it's reason of my problem.

I've added the following reference to my project: Telerik.Reporting.dll, Telerik.Reporting.Wpf.dll and Telerik.ReportViewer.Wpf.Themes (all 3 are pointing on the 2019 trial installation)

But when in my Xaml, i start to write

<telerik:RadReport

or <telerik:Report the intellisense finds nothing.

There are already some telerik components on the test window but they are 2017 Telerik IU for wpf and the namespace currently declared is this one: xmlns:telerik="http://schemas.telerik.com/2008/xaml/presentation"

So, i made a try by using the Component Toolbox, but of course because of my choice during the installation, no telerik's components are registered. So i restart the Telerik Reporting installer and check the 'visual studio integration', but the toolbox stay empty.
So, i try to follow the procedure written there : https://docs.telerik.com/reporting/wpf-report-viewer-manual-setup#how-to-add-the-wpf-reportviewer-to-the-toolbox
But, the Telerik.ReportViewer.Wpf assembly is not listed in the components (i can see all the telerik UI for wpf ones but none for reporting). If i try to use the Browse button to select the Telerik.ReportViewer.Wpf in my fresh installation of TelerikReporting, i have an error message saying :'There are no components in 'C:\Program Files (x86)\Progress\Telerik Reporting R1 2019\Bin\Telerik.ReportViewer.Wpf.dll' that can be placed on the toolbox.'

Ok it seems i have messed up my installation or there's something i don't understand.

What can i do ?

Regards,
Cédric Connes

answered on 06 Feb 2019, 11:33 AM

Hello Cédric,

Indeed, Telerik Reporting WPF Viewer should be used with the corresponding version of Telerik UI for WPF. This is a must - check our Upgrade Path for R1 2019. Note that the WPF viewer is built with Telerik UI Controls for WPF 2019.1.116.40. It is *not* possible to use the WPF viewer with an older version of Telerik UI for WPF.

For the MVVM scenario, I suggest the Using the WPF Report Viewer in an MVVM scenario KB article.
Another sample and more details may be found also in the Reporting WPF MVVM Sample forum post.

You may open a support ticket and send the particular project/business object so that we try to bind it to a data item (e.g. Crosstab) and suggest a more specific solution or workaround.

Regards,
Todor
Progress Telerik

answered on 12 Feb 2019, 09:47 AM

Hi Cédric,

Indeed, the report is just a definition of the report design. It is not meant to be 'NotifyPropertyChanged' compliant. Note that most of the WPF Report Viewer properties will raise property changed.
Our WPF Viewer uses components and themes from Telerik UI for WPF. They can be used without an additional fee only for the purposes of the viewer. The necessary assemblies can be found in our WPF demo folder - Telerik Reporting installation folder)\Examples\CSharp\WpfDemo\bin (e.g. C:\Program Files (x86)\Progress\Telerik Reporting R1 2019\Examples\CSharp\WpfDemo\bin).
You may consider one of our product Bundles that includes both the Reporting tool and the UI for WPF.

Regards,
Todor
Progress Telerik

Product Bundles

DevCraft

Web

Mobile

Document Management

Desktop

Reporting & Mocking

Automated Testing

CMS

UI/UX Tools

Debugging

Free Tools

Support and Learning

Evaluating Report tool for WPF

9 Answers, 1 is accepted