Using Roboto Medium changes values "FVS!dBTI" should be "EUR Cash" (shift characters by 1) weird !!!!
I would like to formally request the ability to "sign" in some fashion a trdp/trdx file. Note that if only the new file format is supported then that would be acceptable.
Basically, I would like to apply some signature that we could, if we so chose, read from the report file to verify that it was us that created or last modified the file.
If we need to use a separate tool to apply the signature other than the report designer, that would not be an issue.
The signature could be anything that Telerik/Progress decides we can use such as a code signing certificate, a strong name, etc.
Using the last modified time, or a hash value created from the current contents of the report file would not be a good solution as that would mean we would need to have a list of the hash values for each report and it would need to be updated every time the report is changed.
We are looking for something that could be applied to all reports that we create and that clients could not replicate.
This would need to be something that clients who we deploy the report files to cannot replicate and therefore if they modify the report file using the Telerik designer, it would remove that signature. This way we can easily programmatically determine if the client has modified the report, and therefore prevent using it as if it is ours.
Note that we provide the ability to use custom reports in our application which are treated as separate from our core provided reports. Also, I had posted to the forum asking if this is currently possible (https://www.telerik.com/forums/sign-telerik-reports).
We need the ability to automatically adapt report layout after its page size chages using report elements docking, anchoring etc. functionality.
This will allow us to reuse report templates for different printer paper sizes without making specific report for each paper size.
We do not have knowledge of internal report layout composition so a layout changes cannot be done with custom code, but need to be specified in reports directly.
I suggest that when saving reports as trdx files (trdp files are no good as they are compressed), that you save the SQL on multiple lines as it appears in the designer to enabled version comparison, i.e. git history of the file's changes can show the changes to the SQL. Currently the SQL is on one line making it difficult to see the history.
Use only components from KendoUI for Angular. It would be understandable that such report viewer would provide less features, but it would remove dependency from jQuery and KendoUI for jQuery.
Actually multi value parameters is not supported on WebServices source. Multi value are passed as [string1,string2] instead of $paramName=string1¶mName=string2. Multi value has to be passed on query string on correct way!
It would be nice if resx files to localize the (wpf) report viewer can be placed in a specific resource path instead of the main folder of the VS project. For example a 'Resources' folder within the 'Properties' folder of the VS project.
A Reporting engine should expose the ability to control the layout of the table of contents\Document Map. Reports are not always data driven and should give the ability to display the contents of the report at different levels, much like Microsoft Word does with their table of contents.
I have a report that has dynamically created html text based on the data. I would like to have a footnote associated with one of those HtmlTextBox controls to appear at the bottom of the page on which the section occurs. Please see a ticket "How to create a report footnote" https://www.telerik.com/forums/how-to-create-a-report-footnote Thank you.
The Labels to be displayed on a Numerical Scale Axis are currently set automatically. The user can control the scale range via Axis Scale Minimum and Maximum properties. The user can control also the Label Step. However, the exact Axis Labels to be shown are calculated automatically and cannot be controlled directly by the user. For example the user cannot force the Axis Labels to start from the Minimum value.