Importing configuration data
You might want to import vault configuration data to:
- Restore a vault’s configuration to the state it was before you made configuration changes
- Use vault objects or options from a different vault to avoid re-creating them manually.
Before you begin Ensure that no users are connected to the vault. Importing vault configuration data while the vault is active can cause errors and potential data loss.
To import vault configuration data:
- In Configurator, on the Vault menu, select Import Configuration. The Import Vault Configuration dialog box appears. The Progress area of the dialog lists all of the vault configuration object types that can be imported. By default, all objects are selected.
- Type the path and file name of the configuration file you want to import in Import from or click Browse and select a file.
- Clear the check marks next to the object types that you do not want to import.
- Click Start to begin the import. A check mark appears next to each object in the Progress area of the dialog that is imported from the specified file.
- Click Details to see the names of each object that was imported or to read error messages.
- Click Close to close the dialog.
Note
- If you import property definitions to an existing vault, the properties will not exist for the objects that use those properties until the next time that the objects are edited. Then the property will be assigned to the object and the new value (if any, including empty) saved. Under most circumstances, this is transparent and is not a cause for concern. However, it should be considered under the following circumstances:
- Navigation views and searches that include the new property. Because folders or documents will not yet have a value (even empty) for the property, those objects will not appear in such a view or search.
- Updating data outside of Meridian, for example, title block or file property updates. Do not assume that a new property added to a document type is empty and will clear an existing title block or file property value.
If the configuration that you are importing refers to .NET extensions (Meridian Asset Management Module 2010 or higher extensions, for example), the error No binary file is available to install extension may appear. If this occurs, register the extensions manually as described in Registering custom interface extensions.
- Just as documents that are deleted from a vault are not permanently removed and can be restored, objects (for example, document types and properties) and references (for example, extensions applied to document types) that are deleted in Configurator are not permanently removed from the vault. The deleted items are exported to the configuration (.met) file and will be added as undeleted items to the destination vault when the configuration file is imported. You must manually delete the items in the destination vault.
- By default, all security roles are granted all privileges to tables that are imported to a vault’s configuration. To restrict the security privileges for a table, see Creating and editing tables.
- Importing workflow definitions will update existing workflow definitions in a vault only if:
- There are no active workflows that use the workflow definition. Release the workflows first.
- There are no document types to which the workflow definition has been applied. Remove the workflow definitions from the document types first.