This documentation supports the 9.1 version of Remedy IT Service Management Suite.

To view the latest version, select the version from the Product version menu.

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).

Note

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.

Content dependencies

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:

  1. 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
  2. Ensure all the items above are already available in the instance you plan on importing the item into

Database independence

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:

  1. Created Virtual Tables within the View
  2. Freehand SQL Calculated Fields in the View
  3. Freehand SQL Reports
  4. 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.

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Ryan Nicosia

    Need to remove the "Free hand SQL report" example under Database Independence.  BMC doesn't support Free Hand SQL reports.

    Apr 26, 2017 08:21
    1. Nidhi Das

      Hello Ryan,

      Thank you for pointing out the issue. I have updated the topic.

      Regards,
      Nidhi

      Apr 27, 2017 12:51
  2. Chakra Tiru

    Hi,

    In reference to limitations to move smart reporting content from one environment to other, I've couple questions

    1. we've views with virtual tables that are joined with standard tables and reports associated to that View. I've exported View/ reports to .XML from dev env. But, at the finial stage of importing .xml in prod, we are getting following error

    "Oh no! An error has occurred during this processing, please try again later"

    Does it mean that smart reporting doesn't support importing views with virtual table and report associated to it?

    1. we've multiple tables at view form level which are purely based out of SQL script (derived). I've used those tables in View and created reports out of it without any issues. However, issue is with moving content to PROD from DEV.

    I get same error message that I mentioned in point 1. Does it mean that smart reporting doesn't support importing Views using tables which are DR tables at view form level?

    Appreciate if you can please provide your feedback on this. We are currently in our initial stages to migrate from BO 4.x to smart reporting 9.1.03. So we want to know what’s available and unavailable so we can plan things accordingly.

    Thank you, CT

    Jan 30, 2018 03:46
  3. Chakra Tiru

    Hi,

    In reference to limitations to move smart reporting content from one environment to other, I've couple questions

    1. we've views with virtual tables that are joined with standard tables and reports associated to that View. I've exported View/ reports to .XML from dev env. But, at the finial stage of importing .xml in prod, we are getting following error

    "Oh no! An error has occurred during this processing, please try again later"

    Does it mean that smart reporting doesn't support importing views with virtual table and report associated to it?

    1. we've multiple tables at view form level which are purely based out of SQL script (derived). I've used those tables in View and created reports out of it without any issues. However, issue is with moving content to PROD from DEV.

    I get same error message that I mentioned in point 1. Does it mean that smart reporting doesn't support importing Views using tables which are DR tables at view form level?

    Appreciate if you can please provide your feedback on this. We are currently in our initial stages to migrate from BO 4.x to smart reporting 9.1.03. So we want to know what’s available and unavailable so we can plan things accordingly.

    Thank you, CT

    Jan 30, 2018 03:46
    1. Vrishali namdev Galinde

      Hello Chakra,

      Apologies for a delayed response. We need to troubleshoot this issue and will require logs for the same. Request you to raise a ticket with the BMC support team for the same.


      Regards,

      Vrishali

      Apr 22, 2019 03:42