Best practices for using BMC Remedy Smart Reporting
This topic describes the best practices for using BMC Remedy Smart Reporting effectively when performing the following tasks:
Creating custom reports
The best practices for creating custom reports are as follows:
- Do not modify out-of-the-box reports provided with BMC Remedy Smart Reporting. However, if you choose to modify a report, ensure that you first create and save a copy of it.
- For better performance, create multiple small reports with only a few columns per use case, rather than creating a large report with many columns to solve multiple use cases.
- While designing a report, we recommend using filter with smaller time frames, for example, 1 day or 1 week.
- We recommend designing a report by using a database with less data in a test environment first, and then importing the report to the production environment.
- We recommend not using Remedy Smart Reporting as an ETL tool which typically deals with high data volume.
For more information on best practices for using Remedy Smart Reporting, see the Yellowfin knowledgebase article at Report Builder.