If you need to limit export options per report, our recommendation is to use CSS to hide the default export option and to add custom UI that uses the HTML5 viewer's exposed API - data attributes
. This will let you load only the export options you want and to trigger export through the viewer.
If you need to limit export options in general for all reports going through the ReportsController in the application, you can add an App.config file
on the root level (this is a hack) and add the configuration in it - Connection Strings and Engine Configuration
The attached demo project illustrates the settings.
On a side note, you can host the Reporting REST Service in a separate project
with enabled CORS
, targeting .NET 461 framework. The viewer in the .NET Core project does not require any Nuget packages, it requests its resources from the Reporting REST Service. Thus you will be able to target more platforms with the client project (the .NET Core project).
I hope this helps.
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items