Please enter search query.
Search <book_title>...
Enterprise Vault™ Discovery Accelerator Administrator's Guide
Last Published:
2021-12-06
Product(s):
Enterprise Vault (14.2)
- Introducing Discovery Accelerator
- Introducing the Discovery Accelerator client
- Setting up and assigning roles
- Working with cases
- Setting up review marks and tags
- Using rules to mark and tag items automatically
- Using Custodian Manager
- Searching for items
- About searching with Discovery Accelerator
- Defining email targets with Address Manager
- Building Discovery Accelerator search schedules
- Manually reviewing items
- About reviewing with Discovery Accelerator
- Searching within the review set
- Deleting items from Enterprise Vault archives
- Working with research folders
- Exporting and producing items
- About exporting and producing items
- Performing an export or production run
- Creating and viewing reports
- Appendix A. Customizing Discovery Accelerator
- Setting Discovery Accelerator system configuration options
- Appendix B. Importing configuration data from an XML file
- Appendix C. Enterprise Vault properties for use in Discovery Accelerator searches
- Appendix D. Troubleshooting
- Issues with Custodian Manager
- Issues with Discovery 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.config
in 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.