The export/import functionality of the Report Module can be used to save the data of a report one or more reports and their datasources to a file on disk and load it them again at a later time or on a different machine.
...
To export one or more reports and their datasources and save them to the hard disk:
...
To import the exported reports and datasources again at a later time or on a different machine:
...
Selecting a name in this lookup will cause the import of the datasource to overwrite the existing datasource by the selected name. This will be reflected by the text in the Action column:
The "Clear" button can be used to clear the Replaced Name column, meaning that the import will create a new datasource without replacing an existing datasource.
The Replaced Name lookup selection box may display the tag "(same origin)" with an existing datasource, signifying that this datasource has a unique identifier that matches that of the datasource that is being imported. Since this identifier is unique and is assigned when the datasource is created, this means that the two datasources were both based on one datasource that was newly created in the past . The matching of origins of the imported datasource and the existing datasource it replaces is also shown in the Action textand are likely different versions of this datasource.
The Action column shows the action to be performed to satisfy all the choices the user has made in the other columns. The following Actions are possible:
| Action | Condition | Explanation | Warnings |
|---|---|---|---|
| Do not import object | New Name is empty | Does not import the object |
ignores it in the rest of the process |
| Import object without conflicts | Replaced Name is empty |
no existing object with matching origin | Leaves object's origin GUID the same |
does not replace an existing object | ||
| Replace object with same origin | Replaced Name has object with matching origin | Leaves object's origin identifier the same |
replaces an existing object with the same origin GUID |
| data from another version of the object may be erased | |
| Split off object from origin | Replaced Name is empty |
an existing object has matching origin | Assigns a new origin GUID |
does not replace an existing object |
| object can |
| no longer be associated with other versions |
| Replace object with different origin | Replaced Name has object with different origin, no existing object with matching origin | Leaves object's origin GUID the same |
replaces an existing object with a different origin GUID |
| data from an unrelated object may be erased | ||
Replace object with different origin. Split off object from origin. | Replaced Name has object with different origin, an existing object has matching origin | Assigns a new origin GUID |
replaces an existing object with a different origin GUID |
data from an unrelated object may be erased |
object can |
no longer be associated with other versions |
The Reports tab of the Import Wizard shows exactly the same grid as the one in the Datasources tab, except applying to the Reports that were stored in the .rpx file.
One scenario unique to reports that may occur is that the datasource that a report depends on was previously chosen not to be imported, meaning that the report itself can also not be imported:
If you do want to import the report, return to the Datasources tab and make sure the datasource of the report in question is imported by making sure that the New Name field is filled in.
On the Finish tab, an overview of all the actions to be performed for the import is shown. Here you can review the actions to make sure everything is as expected:
Click Finish Import to perform the actions as displayed. This will return you to the Reports Overview, where your imported reports can then be found.