Enterprise Vault™ Compliance Accelerator Administrator's Guide
- Introducing Compliance Accelerator
- Product documentation
- Introducing the Compliance Accelerator client
- Setting up employees and employee groups
- Assigning roles to employees
- Working with departments
- Implementing Chinese Walls security
- Managing exception employees
- Grouping departments into partitions
- Using attributes to classify departments
- Searching for items
- About searching with Compliance Accelerator
- Building Compliance Accelerator search schedules
- Defining hotwords to search for
- Manually reviewing items
- About reviewing with Compliance Accelerator
- Escalating items
- Working with research folders
- Exporting items
- Creating and viewing reports
- Available Compliance Accelerator reports
- About viewing Compliance Accelerator datasets using the OData web service
- Appendix A. Customizing Compliance Accelerator
- Setting Compliance Accelerator system configuration options
- Appendix B. Importing configuration data from an XML file
- Appendix C. Troubleshooting
- Issues with Compliance Accelerator reports
Reports that you export as CSV may not open properly in Microsoft Excel
By default, SQL Reporting Services exports CSV files with Unicode encoding rather than ANSI encoding. The data in a Unicode-encoded CSV file does not tabulate properly when you open it in Microsoft Excel.
To work around this problem
- Locate the file
rsreportserver.configin the SQL Reporting Services installation folder.
- Open the file in a text editor such as Windows Notepad.
- Comment out the following text block by enclosing it in the marks <!-- and -->:
<Extension Name="CSV" Type="Microsoft.ReportingServices.Rendering. CsvRenderer.CsvReport, Microsoft.ReportingServices.CsvRendering"/>
- Add the following text block:
<Extension Name="CSV" Type="Microsoft.ReportingServices.Rendering. CsvRenderer.CsvReport, Microsoft.ReportingServices.CsvRendering"> <Configuration> <DeviceInfo> <Encoding>ASCII</Encoding> </DeviceInfo> </Configuration> </Extension>
- Save and close the file.
After you have edited the configuration file, SQL Reporting Services ignores any Unicode characters that were stored in the initial report.