Only authorized users with appropriate company permissions and accesses can use the export and import features.
ActivReporter provides wizards to help you with exporting and importing data. Files are exported in XML format, a format which preserves the important details of your records as you move them. You can use export and import to move data from one ActivReporter company to another. You can import data from an outside source into ActivReporter. You can use export and import to move data between ActivReporter and third party programs.
The export feature is available nearly everywhere you find data in ActivReporter; the import feature is available for most data which is not read-only. You can export all records in a folder, selected records in the HD view, or a single record open in its native editor.
In the Navigation pane, highlight the entity folder to import records into.
Right-click and select Import from the shortcut menu. The import wizard starts.
In the File field, click to open the Browse window.
Navigate to and highlight the file to import.
Click Open. The path and file name load in the wizard.
Click Next >>. ActivReporter prompts you to confirm your action.
Click Yes.
When the import completes, click Finish.
Default import behavior
When importing an XML file that contains one or more entities, the default behavior is to create a new entity for each XML data element. You can override this behavior by adding the "Command" attribute with values of "New", "Edit", and "Delete" to the data element.
The order that you import data into ActivReporter is important. If the data you are importing depends on other data that hasn't been imported yet, your import will fail.
You cannot import entity records that reference other entity records which are not in the destination database.
Example
Permissions that reference authorized users who are not yet in the destination database cannot be imported. You may need to import or create the authorized users first. Security can be particularly thorny since authorized users can reference permissions and security views and permissions and security views can reference authorized users.
You cannot import entity records that reference custom data which does not exist in the destination database.