It would be useful to have tooltips to graph series  so we can explain what each Series is showing.

We'd like to distribute the standalone report tool to our clients and provide data through a web service. We don't want to have to redistribute a dll everytime we make new data available.

The standalone report tool should be able to query our webservice for what data is available and then allow the client user to create reports from it.  i.e. obtain list of table names dynamically as well as their column names and data.

A possible solution is to allow the tool to view and interact with classes in an external assembly that are dynamically generated with Reflection.Emit.

This is your reply to one of our questions regarding RTL support of crosstab component.
"The Crosstab item will not change its layout (does not support RTL layout flow). You will have to create to separate reports with similar layouts. One report can be used with RTL languages, and another with LTR languages.
Note that row groups can be added only on the left side of the Crosstab item. "
SO our request is to fully supports RTL.

In general, the Page sections do not collapse or expand based on their content. Also the report header and group header sections span the width of the column.

It would be nice if, for example, have another section that either could expand/collapse based on the content and do not be affected by the report's page settings.

As for now, the workaround is to use the series' DataPointStyle.BackgroundImage property to add a custom image as a marker. Then, to change this image based on the condition you can use DataPointConditionalFormatting property.

The Marker Types I am using are commonly used e.g Square, Plus, Cross. Please add an option to set Marker Type for the values instead of background Image.

It would be very handy, if the value property of the PictureBox would resolve images from base64 strings besides the Image, Image byte[], relative or absolute URI.
It should be fairly simple to implement. I wrote my own user function for this. It would be beneficial to have this out of the box.

[Function(Category = "Image", Namespace = "ImageFunctions", Description = "Converts a base64 string to an image byte array")]
public static byte[] ConvertFromBase64(string imageString)
{
    if (imageString != null)
    {
        // Convert base 64 string to byte[]
        byte[] imageBytes = Convert.FromBase64String(imageString);
        return imageBytes;
    }
    else
    {
        return null;
    }
}

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.

Hello,

I see from support threads that Telerik really resists any changes to their concept of CSV rendering.  And I also understand the reasoning in not changing any default behavior due to its potentially unwanted effect on established customers.

That said, I wonder if the ability to exclude hidden objects (TextBoxes for example) has been proposed and is in the list of potential enhancements.  I wouldn't mind if it required a configuration setting like NoHiddenObjects = True where the default is False.

Has that been considered?

We are using the external style sheet file (StyleSheet.xml) when designing our report from Web report designer. We want to see our style sheet applied on our report when we see the report from Web designer in design mode. In Preview mode it is working fine.  But the problem here, it is not working in Design mode.

See the attached pictures. You find our problem on the picture ExternalStyleInWebDesigner-DesignMode.PNG

Is there any solution or a feature request needs to be created?

FYI: External style sheet is working in Standalone report designer in both design and preview mode.

Thanks,

If I put the following content in an HtmlTextBox, when I open the preview mode of the designer or look at it in the Html5 Report Viewer I get annoying extra gaps:

<p>Comment</p><p>Comment</p><ol><li>List</li><li>List</li><li>List</li></ol><p><br></p><p>Comment</p><p>Comment</p>

I tried to replace these <p>-tags with <div>-tags:

<div>Comment</div><div>Comment</div><ol><li>List</li><li>List</li><li>List</li></ol><div><br></div><div>Comment</div><div>Comment</div>

It helps. But there are some other tags that cannot be replaced (tags of ordered and unordered lists for example). And these gaps are still rendered. 

Enable retaining editable textboxes when Exporting to PDF.

For example a PDF Re-order form with editable textboxes for order Quantity so the user can enter order Quantities.

We use Telerik reports for many different things.  We generate reports, letters, mailings, excel documents and forms or applications.  Our applications can either be blank or pre-filled or completely filled with information from the user.  Now I realize that you can say that all of these are forms of reports, but I would submit that is only partly correct.  I tell people that Telerik reports is a way for me to produce output that can be electronically distributed or printed.  While that is a definition of a report, I think it can go a bit further.

If you think about PDF forms and what they are, they are a report that allows the user to add additional information and send back to the customer.  I do realize that some features of PDF forms allow for scripting that can automatically submit, and there is a lot of other capabilities that moves PDF forms outside the realm of basic report generation. That being said, the ability to set a parameter in a report whereas the fields are replaced with basic text input PDF fields would be a huge advantage for Telerik.  I could see them opening up the forms generation market for this product.

While I have no input into your roadmap and, as a former Product Architect for a software development firm, I fully understand scope creep and keeping product focus, I would love to see:
1) a parameter export to PDF that converts the fields (everything that has a Fields.XXXX keyword somewhere in the value property) to PDF form text fields without adding data.  I would set the length the same way you set the horizontal length of the field on the report.
2) a parameter on a field item that says this field cannot be converted into a form field and must have data.
3) a parameter on reports indicating that when generating PDF form fields, that X number of rows are generated for the detail section.
4) if a field value is too complex or if the report is too complex, I would just fail over to a blank value.
I realize there are a lot of capabilities in PDF forms, but I tried to keep my wish list confined to the basics that would allow for easy additions to support advanced capabilities post report generation.

All this being said, I have communicated to my customers that Telerik is not going to support PDF form fields and we have an upcoming meeting to discuss this requirement.  I have a lot of resources, time and money invested in the development of Telerik reports and it is a concern that I may have to remove Telerik reports from our solutions because of a need to support this PDF capability.  We have reports on multiple different platforms and I feel that Telerik Reports is one of the best in terms of use on many different styles of applications. But since I am a firm believer in using as few technology vendors as possible (and only want a single reporting solution), I am concerned about having to re-architect our solution reporting infrastructure to remove Telerik reports.

if you can provide a default resource file of report designer, and provide the same name convention rule of the resource file, then we can translate it by ourselves.

DocumentMap is using the order of report structure to create the tree. For the moment, the only way to change this order is using "Bring To Front/Send To Back" in report designer, which is badly named in this case, and awkward to use.

You should:
-add Bring Forward/Bring Backward functions
-document in DocumentMap help section that theses functions will also change the order in the report structure.

Ideally, a move up/down in report explorer view would be even better (and more intuitive).