As in Ticket with ID 1440072 requested we are looking for a funktionallity to send Reports via E-Mails with the WPF ReportViewer. As only the HTML-5 ReportViewer currently supports the E-Mail sending we would request the feature for WPF as well.

 

Best Regards,

Martin

When a date is set as a report parameter in the HTML5 viewer, it formats the parameter as a JSON date using a timezone.  Where no time is specified this results in a time part added to the date when received at the server.  This is a problem, especially for browser in a negative offset zone, e.g. US, where upon the date goes to the previous day.  Please add support for parameter types of date, where no time is present and no conversion is done anywhere.

If a user desires to send a report by email, the recipient will receive the message from a generic email and if the recipient wants to respond, the response will go to a mailbox that is not monitored. On the other hand, if we use the "From" field and we try to do a "legal spoofing," some email servers will send our messages to spam or simply block them. It could be great to have an option to ask users their email password in the moment when they click on the button to send a report via email. In this way we can send the information in the field "From" and the password entered to the SMTP server.

This will prevent file caching.

The image box should allow selecting how the image should be aligned within the box.

Ie, if I select ScalePorportional, it will always center the image either vertically or horizontally. I should be able to further align it to the one or two of the sides of the box. This would allow say the upper left corner of the image to always be locked in place.

Currently, there is no natural way to disable picturebox errors. Sometimes we do not care to know that the image wasn't found, especially when the error shown severely damages the look of the report, stretching and pushing things out of the way. The image URL may be built via parameters, pointing to a large folder where photos of a given employee may or may not exist. It took multiple unhelpful support tickets, many headaches and days of research to finally find an obscure post by a private individual with an undocumented custom solution that worked. 

Add the ability to specify rounded corners for the border of TextBoxes, Pictures, Tables and all other similar controls.

We create many legal forms, which use nested ordered lists. In htmlTextBox for reporting, we'd like to apply styles like upper-alpha, lower-alpha, etc to the ol tag. Currently, the only numbering for an ol is 1, 2, 3. CSS ability to set the style at depth (like ol ol) would be best.
<ol>
<li>1. text</li>
<li>2. text
  <ol>
  <li>a. text
     <ol>
          <li>i. text</li>
          <li>ii. text</li>
      </ol>
  </li>
  <li>b. text</li>
  </ol>
</li>
</ol>

For our Customers a major drawback to creating form type reports (Invoices, Purchase Orders etc.) using Telerik Reporting is the inability to show vertical dividing lines between data columns in the 'Detail' section of the report that extend all the way down the page to the Page/Report footer. We were able to do this with Crystal Reports. But we plan to migrate all our Crystal reports to Telerik.

I would like to be able to do this syntax: Fields.Address?.State.  If address is null, then it is the same as state being null.  Instead of displaying an error, it would just show blank.

Please add support for Data Matrix barcodes.  As of Q3 2014 this is the only format we will still need to rely on another library to create an image that is placed in a picture box.  We would much rather be able to use the Barcode control for all our barcode requirements.

Please, add functionality that allows the user to print the Grouping value on each page if its content does not fit on one page.

Hi,

Most design programs allow the user to select and object and "nudge" (move) up, down, right, left in very small increments.

I miss this feature in the report designers.  Always have to use the mouse is not the best experience in tight places.

Please add this capability.

Some programs also have variations of the feature base on the if the user presses CTRL+ {ARROW} or SHIFT + {ARROW}

Thank you,

Karl

StyleRule Collection Editor Members list NEEDS to be resizable. 

PLEASE SEE THE ATTACHED IMAGE

It's frustrating to have to scroll a Listbox horizontally to read the values. 

This control should be wider by default, and then allow the user to resize, and then REMEMBER their resize.

Thank you,

Karl

Hi,

It gets frustrating always resizing every dialog so I can use it, each time I open them.

Please give the Report Designer Dialogs, and Visual Studio dialogs a save size setting so when reopened they will go back to the same size.

Thank you,

Karl

Hi,

It's very frustrating having to type in Style Names in the Properties tool window.

All styles names both internal and external should be known by the standalone designer or Visual Studio designer.

This would be a big productivity boost.

Karl

I have scenario like this: Sam requests a product report from company A.  Marvin creates the report and send it back to Sam.  Sam imports it.  It would be best if Marvin (Author of the report) could specify all the meta data so that Sam doesn't have to enter these things.

In my case I need following metadata for the report:

• Keyword: some external tags...
• Description: a description so that the user can understand what this report will show and the purpose of the report.

To have a better performance would be nice to cancel report rendering automatically or manually. 
If I am asking for a big report and after I change parameters and request new report, the previous request is still in progress and it is not going to be cancelled. Therefore I see high memory consumption on continuously refreshing a reports with a big data and after some time I see complete slow down of the Reporting Service and of course slow down of the server itself. The memory in this case is not released and Reporting Service crashes sometimes.

Please put the tool windows in a Docking system, like Teleriks.  Forcing the property window to be pinned to the right side is a UI/UX issue. Studies have shown that placing it on the left, makes it easy to use since the object your assign property value is very close and the distance the mouse must be moved it greatly shortened.

For the font's using the Windows DPI settings is not enough and won't cover use cases.  I always run my system at 100% Font Size and then adjust each application individually as required.  

If you use the Windows font settings, users will have problems.