Blogs

.NET to SQL to Project Server and everything in between
Welcome to Blogs Sign in | Join | Help
in Search

Strate SQL

Disabling Export Options in Reporting Services

The other day, I was asked how to disable export options for one of the reports I am developing at my current client.  Having not fielded this request previously, I checked the around found you are able to disable export options for each reporting services instance

In the rsreportserver.config file you can set Visible="false" on the <Extension> elements in the <Render> element that shouldn't be accessible.  This also affects the email delivery extension.


<Render>
    <Extension Name="XML" Type="Microsoft.ReportingServices.Rendering.XmlDataRenderer.XmlDataReport,Microsoft.ReportingServices.XmlRendering"/>
    <Extension Name="NULL" Type="Microsoft.ReportingServices.Rendering.NullRenderer.NullReport,Microsoft.ReportingServices.NullRendering" Visible="false"/>
    <Extension Name="CSV" Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering"/>
    <Extension Name="IMAGE" Type="Microsoft.ReportingServices.Rendering.ImageRenderer.ImageReport,Microsoft.ReportingServices.ImageRendering"/>
    <Extension Name="PDF" Type="Microsoft.ReportingServices.Rendering.ImageRenderer.PdfReport,Microsoft.ReportingServices.ImageRendering"/>
    <Extension Name="RGDI" Type="Microsoft.ReportingServices.Rendering.ImageRenderer.RemoteGdiReport,Microsoft.ReportingServices.ImageRendering" Visible="false" LogAllExecutionRequests="false"/>
    <Extension Name="HTML4.0" Type="Microsoft.ReportingServices.Rendering.HtmlRenderer.Html40RenderingExtension,Microsoft.ReportingServices.HtmlRendering" Visible="false" LogAllExecutionRequests="false"/>
    <Extension Name="HTML3.2" Type="Microsoft.ReportingServices.Rendering.HtmlRenderer.Html32RenderingExtension,Microsoft.ReportingServices.HtmlRendering" Visible="false"/>
    <Extension Name="MHTML" Type="Microsoft.ReportingServices.Rendering.HtmlRenderer.MHtmlRenderingExtension,Microsoft.ReportingServices.HtmlRendering"/>
    <Extension Name="EXCEL" Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering"/>
</Render>



The problem with this solution though is that it is for the entire reporting services site.  If only one or two reprots need a certain extract type removed, you need to either remove the type for all extracts or live with the issues that exporting to that extract type causes.

There should be properties on each report that will disable or enable extract types.  I can't see how it would be that difficult to store this information and access it rendering the report.  The toolbar is already reading an XML file to determine the extract types to make available, it should be a significant leap to query this information from the database as each report is called.
Published Wednesday, May 10, 2006 9:38 AM by Jason

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

Lester Temple said:

How would you disable the Export options from the DropDownList when rendering the reports in a ReportViewer Web Control ??  I've set visible=false on the Reporting Services server, but it doesn't seem to communicate it to the ReportViewer web control.

Thanks,

LES
September 19, 2006 12:12 PM
 

Mike Mason said:

If you're using a ReportViewer control, I've figured out a way to programatically disable  rendering extensions. You can do this on a per-report basis if you like. More info here:

http://mikemason.ca/2007/04/30

April 30, 2007 5:14 PM
 

CB Thirumalai said:

Hi Mike,

In your code,

Extension rsExtension = info.GetValue(extension) as Extension

the rsExtension value is coming as 'null'.  Please suggest where I am going wrong.

July 6, 2007 3:31 AM
 

Boy Meets World » Blog Archive » Disabling Export Formats in Reporting Services said:

December 28, 2007 10:37 AM

Leave a Comment

(required) 
(optional)
(required) 
Submit
Powered by Community Server, by Telligent Systems