I created a report and am exporting it as an XLS.  How do I set the Scale of the report so that when I open it up in Excel it shows as 60% instead of 100%?

thanks

Hello,

I have designed a report with the report wizzard and used the table template for the layout. The dataSource comes from an azure sql database. In preview and html preview I get all records displayed properly on one single page ( ... notice that the entry in Report.Properties.ApplicationSettings.DataSource is set to 'none' !!).

Now I want to group the records, but when I go to add new group, in the 'Edit Grouping / new expression' there is no field to select.

Otherwise, when I enter in Report.Properties.ApplicationSettings.DataSource the same dataSource that I selected when the report was built with the wizzard, I can select a field in the 'Edit Grouping' dialog -> but then in preview and html preview I get 101 pages each with all the same records on it (besides it takes a lot of time to show them eventually).

Please help

Regards, Manfred

Hi,

I was using the Telerik reporting which uses SubReports, everything was working on just fine on Telerik Reporting Q1 2016 SP1 (version 10.0.16.204) but upon updating the version  to telerik reporting R3 2016 (version 10.2.16.914) it stopped working, it looks like the lifecycle has changed. 

<select all> is missing in html5 for MultiValue parameter.

In the report designer I see the <slect all> option but it does not display in the html5 version.

How can I get that to display correctly?

Marty

Hello,
here is a list of problems I find with the WPF report viewer and some possible enhancements:

1. In the print preview mode, when the zoom is set to ”Whole page”, the code calculates a zoom factor. Doing so, it makes a round of the value, instead of a ceiling. The result is that, depending on the size of the window, there are sometimes a scroller that is shown and active. For example, if the zoom to display the whole page is 108.4%, it is displayed with a zoom of 108% and the scroller appears.

2. The whole control is enclosed in a border. In the case the control is displayed in a window, and only it is in the window, this border should not be there: please add an option to disable the border. At least, bind the BorderThickness property of the control to this border.

3. There are 2 display mode: Interactive view and print preview. In some cases, the interactive view is not useful, so there should be a way to disable the button, or better remove it. At the same time the button is removed, you should also remove the first 4 buttons, which are only used in this mode.

4. The export button content should be customizable: we should be able to specify which formats are displayed there.

Patrick
-         
In
the print preview mode, when the zoom is set to ”Whole page”, the code
calculates a zoom factor. Doing so, it makes a round of the value, instead of a
ceiling. The result is that, depending on the size of the window, there are
sometimes a scroller that is shown and active. For example, if the zoom to
display the whole page is 108.4%, it is displayed with a zoom of 108% and the
scroller appears.

-         
The
whole control is enclosed in a border. In the case the control is displayed in
a window, and only it is in the window, this border should not be there: please
add an option to disable the border. At least, bind the BorderThickness
property of the control to this border.

-         
There
are 2 display mode: Interactive view and print preview. In some cases, the
interactive view is not useful, so there should be a way to disable the button,
or better remove it. At the same time the button is removed, you should also
remove the first 4 buttons, which are only used in this mode.

-         
The
export button content should be customizable: we should be able to specify
which formats are displayed there.

In our UI, the user has the ability to export their reports to multiple formats including PowerPoint.

We have noticed that the PowerPoint exports don't always work.  Sometimes, the reports will go to PowerPoint with not issue and sometimes they it seems the export will just stop and the download is never received.

One thing that I have noticed is the reports that return larger amounts of data seem to not work as reliably.  They will render in the report viewer, but the PowerPoint export never shows up.

Any help is appreciated.

Thanks,

Phillip

Hello,

We have recent upgraded from Reporting Q2 2015 SP1 to Reporting R1 2017 SP2 11.0.17.406 and we are having an issue with report books. Anything that causes a refresh causes all of the parameter viewstates to collapse. If we fill them with pre-saved values and attempt to display the report book, they also collapse and rendering the book fails because no parameters can now be found. Not experiencing this issue with single reports, only report books.

Is there somewhere i should be looking specifically to address this? Using VS2017's debugger did not help much, only to show that the viewstates are gone before the first parameter is ever retrieved. Any insight would be most appreciated.

We are in the process of creating a WPF version of our application that is already written in Silverlight.  We rely on Telerik controls across our entire UI and we've been very happily surprised with just how easy that process has been thanks to the common interface between Telerik's SL and WPF controls.

However, we have started porting over our logic that deals with the Report Viewer control and have noticed that the ReportViewerModel class is internal in WPF whereas it is public in Silverlight.  I've read many forum posts that talk about how the ReportViewerModel class is meant for internal use and can change at any point.  Despite that, we've very happily depended on the ReportViewerModel class because we do a lot of 'deep' integration with the Report Viewer.  If the internal structure of the Report Viewer changes, we aren't surprised if we need to tweak our code and just accept that as the cost of being tightly coupled with the Telerik controls (on a side note, we have the same situation with the Telerik Grids and other controls where we are also deeply integrated).

In reading through other forum posts, I know you tend to point people towards using methods on the Report Viewer instead of going to the model.  I briefly looked into that but there are some functions that just don't seem exposed on the Report Viewer (one example is setting IsExportEnabled on the model which doesn't seem to have any corresponding way to set that from the Report Viewer).

Even if there were ways that we could change our logic to avoid using the ReportViewerModel, I'd still feel much more comfortable if our existing code that has been heavily tested and scrutinized could 'just work' in WPF.  We want to avoid as many major refactorings as possible and it seems like we could avoid a whole bunch of headaches if this class could be public like it is in SL.

Hi,  

I'm using the kendo html5 report viewer to display my kendo Reports on my MVC app; however i'm having trouble to understand why do my reports/queries take much longer to display on my app than it takes to display on the vs report designer.

Is that normal and is there anything that it can be done to improve the performance of the reports on my application? 

I want to do conditional formatting on a particular column called "HubArrival" which is DateTime format. I want it to have a pink background if the difference between HubArrival and BookedArrival is greater than 45 minutes, and I have set up conditional formatting to do this. Here is the code from the resulting designer file:

formattingRule2.Filters.Add(new Telerik.Reporting.Filter("AddMinutes(Fields.BookedArrival, 45)", Telerik.Reporting.FilterOperator.LessThan, "Fields.HubArrival"));

On running the report, an error occurs stating that DateTime cannot be compared with text - but both fields are of type DateTime.