Export and import repository
BMC Remedy Smart Reporting provides you with the capacity to export all your content definitions including the related entities from one instance of BMC Remedy Smart Reporting (e.g. QA) and import these into a separate instance (e.g. Production).
When exporting definitions from BMC Remedy Smart Reporting there are certain limitations. You cannot export security settings that relate to individual users, only group or roles. These will have to be reset when importing them into the new instance of BMC Remedy Smart Reporting. Source filter information will be exported but only if it is a scheduled SQL query. Manual records and data file records will not be exported. This is because it's assumed that users will differ between instances, but groups and other structures will be the same.
For more information about the export and import repository, see the Yellowfin documentation at Export and import repository.
When exporting content, it's important to not only select the items you wish to export, but also all other items the main content may depend on to work.
BMC Remedy Smart Reporting's content dependency structure is illustrated to the right.
For example, if you are exporting a Report you will need to either:
- Include all images it uses, the category and sub category it's stored in, and the view and source connection it's based on, or
- Ensure all the items above are already available in the instance you plan on importing the item into
If you are using the export and import functions to migrate BMC Remedy Smart Reporting across platforms then you will have to be mindful of any hard coded SQL. examples of this may be:
- Created Virtual Tables within the View
- Freehand SQL Calculated Fields in the View
- Freehand SQL Reports
- BIRT or Jasper reports with platform specific SQL
BMC Remedy Smart Reporting cannot test for these SQL anomalies and you should test your export and import processes across platforms in your test environment prior to migrating into production.