Setting the ParametersAreaVisible and DocumentMapVisible to False in the Xaml, or in the initialization code of the WpfReportViewer doesn't hide the corresponding areas.
The issue is reproducible in .NET Core and .NET Framework.
I want each time a user logs out from my application its session in the Reporting REST Service also to expire. I tried to perform the Unregister Client request with a custom code. However, I need the clientId and there is no straightforward way to get its value from the viewer.
It turns out that the Reporting REST Service keeps its own client sessions that are different from the hosting application sessions. For that reason, the Telerik Reporting REST Service doesn't know whether a user is logged in/out in the main application. Therefore, a Logout functionality in the viewer will be beneficial for scenarios like the described one.
We use Html Report viewer for rendering reports based on Telerik Reporting.
We observe the following issue with report parameters with AvailableValues configured and Multivalue = true:
When there are one or more items from the available options selected - manually unselecting all of them leads to rendering a report as if the last unselected option is still selected leading to wrong result
All other operations over the multivalue parameter work fine.
The issue occurs only in List type Parameter editors. With ComboBox editors this works as expected.
The HtmlTextBox renders less space between the bullet point and text:
Below is the outcome from design time:
And here you see the outcome from the preview:
Telerik,
This is a feature request to allow a designer to set the locale at preview time.
We work on reports that are deployed and executed in many regions and locales around the world.
We cannot have our report designers switch the locale each time they need to test or validate a report, it would become too cumbersome.
Would you be able to add an option (default: Current locale) to the "Preview" screen in the designer that allows the report designer to set the locale to Preview the report as.
Thanks!!
Shawn
The error will be displayed when SkipBlankPages is False.
Exporting a report as PDF produces a corrupted file as soon as it reaches 2GB or more in file size. Available client memory should have been enough and was not at its limit. We have built the application as x64.
We use large-sized image files in the reports.
I have DataSource assigned to my report, which content is displayed in its Detail section. The Page sections have some static content. The SkipBlankPages property is set to False.
When the data set received by the report is empty, the static content in its Page sections is not displayed in Interactive View. In PrintPreview the Page Header/Footer content is displayed as expected. When the data set returns valid data, the Interactive view displays everything as expected.
I've run into a problem when using a Combo Box for a Multi-Select Parameter. The issue is that if the user selected values then clicks the preview button, while the dropdown list is still displayed, the parameter is not set before the report is generated.
I would prefer to use the combo box to set the parameters, but this will be an issue for the users. If I click elsewhere on the report or just re-run the report the parameters are set properly. This does not occur with the Listbox functionality.
The error below is thrown in PictureBox when System cryptography Use FIPS compliant algorithms is enabled:
An error has occurred while processing PictureBox 'pictureBox1': Exception has been thrown by the target of an invocation.--------------- InnerException ---------------
This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
When a report includes drill-down item(s), the report is run again each time the user expands a drill down item. This is apparent in the demo at https://demos.telerik.com/reporting/product-sales
I would like to see all of the drill-down data generated and delivered with the initial report, but collapsed and awaiting inspection.
Perhaps this would be an attribute of the drill-down element (pre-fetch versus re-run) so that developers can choose the most appropriate experience for their users / conserve server resources.
It would be great if you could make the border of the stand alone report designer visible. It's hard enough to see and grab thin gray lines but Report Designer borders become invisible. Below is a screen shot of the report designer in front of my Telerik Reporting program folder:
Our team is in the process of converting Crystal Reports documents over to Telerik Reporting and one of Crystal Reports advantages over Telerik Reporting was the ability to create custom fields with Crystal or Visual Basic Syntax, including the declaration of variables. Lack of variables and a few common constructs can make simple expressions overly complex.
One of the more common use cases for us is formatting text differently based on one or more other values. Without the ability to write if/elseif/else blocks we wind up with nested ternary statements which can be are hard to read and maintain.
While we can write user functions that seems impractical for long term maintenance and support. It would be very helpful if we could create expressions using C# directly in the Report Designer and have the embedded within the report itself.
See my initial request for something similar in the forms here: https://www.telerik.com/forums/feature-request-if-elseif-else-and-or-switch-statement-support-in-expressions
<Nullable>enable</Nullable>validation errors are returned for endpoint which accept null (or nothing) for parameters.
Currently, when GroupFooterSection.PrintAtBottom is set to True, all subsequent sections will be moved to the next page. For that reason, the Report Footer also moves to another page even when its PrintAtBottom is True and both sections can fit on a single page.
If I set the Group Footer PrintAtBottom to False, it will be printed just below the Detail section, which may leave unwanted blank space between the Group Footer and the Report Footer.
I think that it is more intuitive to have both the Group Footer and the Report Footer printed at the bottom of the last page in this scenario, with the Group Footer just above the Report Footer.
In Web Report Designer I added a List to my report groupHeaderSection and then couldn't delete it. It switched it to a TextBox. When trying to delete the TextBox the number of the box increments up/down.
There are times when I can't drag it to a different location.