Good afternoon. When I export a report with a crosstab that contains vertical titles to PowerPoint, the titles are not visible. Please could you help me fix it. Thank you.
Much like the way Excel has the ability to utilize VBA functions. it would be usefull and more conventient for developer if they could include custom functionality/functions in a report rather than use an external assembly. The steps involved to include/use an external assembly is daunting at best and not at all straight forward.
Something like you right click the report and one of the menu options is "Add Custom Function". Or in the expressions dialog box have an option to create/add a custom function.
You get the point. I'm sure your team of developers could come up with something.
Hi Support Team,
There an issue for exporting report to PowerPoint when there is grouping in table and tables goes to next page,
I got this error : "The given key was not present in the dictionary"
I've attached sample trdx file for your consideration.
The problem is not getting the error via Dot Net programming, but the complete layout destruction of the report as a result of the fact that a picture (in our case a thumbnail of a provider) is unavailable. Catching the report error is not an option. It is too complicated and even if we succeed in obtaining the error, it will be very complicated to remove the unavailable url on the fly and re-render the report again. This seems to be a "known issue" for about 8 years! My question: Is it possible to keep the remaining report "intact" if such an error occurs? This shouldn't be too difficult for the development team..
I had a very challenging time getting Telerik Reports to work with my business objects. I'm not the only one -- see this thread: http://www.telerik.com/forums/how-to-use-object-data-source-in-report-designer This could be improved by: 1. Don't make users manually edit <Telerik.Reporting>. Create a UI in the designer where DLL's can be manually selected. 2. If there are errors loading the DLL's in <Telerik.Reporting>, tell the user, rather than failing silently, which is the current behavior. Importing reports from DLL's has the same silent-failure behavior: if there's something not quite right about the DLL's (wrong architecture setting, for example), you just see "no reports to import" rather than the actual error (bad file format, or whatever). I think a little work on the user experience around custom business objects would make new users who want to use the stand alone report designer in this way much happier. I was really surprised and frustrated that a modern product would fail like this with no exposed error messages.
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.
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.
add the possibility of show the parameters area on right/left/below of report viewer.