Exporting Reports with Sub-reports most likely will not import into a new tenant correctly without intervention. Using Tenant copy to copy these types of repots may also result in errors.
Reports have a report ID just like an Event does. The steps to exporting a report with sub-reports to import into another tenant should follow this process.
In the Tenant where the existing report is:
- Download XML of main report and all sub-reports.
- Enter just the Reports section, not the Insights Admin area.
- Open each sub-report and note the report ID in the address bar.
- Go into the new tenant.
- Import Sub-reports only into the new tenant.
- Enter just the Reports section, not the Insights Admin area.
- Open each sub-report and note the report ID in the address bar.
- Open the XML of the main report in Notepad++ or other text editor.
- Search for the original Report IDs (from the original tenant) and replace with the new Report IDs (on the new tenants) - Do a control+F on "sub" or "report"
- Save the XML and import into the new tenant
- Open the editor of the new main report and double check the sub-report references (you may have to point them to the correct sub-reports.
For Templates with Sub-reports
- Download XML of main report and all sub-reports.
- Enter Insights Admin area.
- Open each sub-report and note the report ID in the address bar.
- Go into the new tenant.
- Import Sub-reports only into the new tenant.
- Enter just the Reports section, not the Insights Admin area.
- Open each sub-report and note the report ID in the address bar.
- Open the XML of the main report in Notepad++ or other text editor.
- Search for the original Report IDs (from the original tenant) and replace with the new Report IDs (on the new tenants) - Do a control+F on "sub" or "report"
- Save the XML and import into the new tenant
- Open the editor of the new main report and double check the sub-report references (you may have to point them to the correct sub-reports.
From a post by Kevin in Slack. To see behavior when you don't do this, see this Slack thread.
Comments
0 comments
Article is closed for comments.