Exclude Existing Property Values When Importing a Vault

When creating a new vault in order to migrate data from an existing vault, you have the option to exclude unwanted property values from the new vault. This is possible not only for released or in-progress documents, but also for previous releases or deleted documents. The task that follows will remove the property values completely, even in history.

Note:

This task does not prevent the property definition itself from being imported into the new vault. The property definition will exist in the vault but the imported documents will not have any values for the excluded properties. It is not possible to remove a used property definition. To remove the unused property definition, delete it as described in Create And Edit Custom Properties.

To exclude property values during import:

Create a new text file and give it a descriptive name (for example, ImportFilter.ini).

This file should contain the following information:
- A section named [Generic].
- Under the [Generic] section, a setting named Vault equal to the name of the vault to import (for example, Vault=EDM).
- Optional: Under the [Generic] section, create settings as necessary using the descriptions in the following table.
- For each property set in the source vault for which you want to exclude property values, create a section in the file with the internal name of that property set (for example, [Custom]).
- For each property set section, create a setting for each property that you want to exclude and set it equal to 1 (for example, ChangeManagementDateCompleted=1). Omit properties that you want to include in the import to the new vault.
Add a string type value named ImportFilterFile to the registry of the Meridian application server under the following key:
```
HKEY_LOCAL_MACHINE\SOFTWARE\Cyco\AutoManager Meridian\CurrentVersion\OML
```
This value should contain the path and name of the import filter file that you created in step 1.
Using the Administrator tool, create a new vault using the existing vault as input as described in Create a New Vault.

After the import, the new vault will not contain the property values specified in the import filter.

Optional filter file settings
Option	Description
NoHistory	When this setting has a value of 1, no history will be imported to the new vault. Omit this setting if you want to import all prior revisions of documents.
NoSequences	When this setting has a value of 1, no sequence numbers will be imported to the new vault. Sequence numbers are often used for programmatically calculating object names such as documents. Omit this setting to import the current values of all sequence numbers so that new objects in the new vault continue the sequences begun in the old vault.
SplitImportFrom	When this setting has a value of 1, the source file path is split into a path and a file name and stored in the AMFSObjectPropertySet._IMPORTEDFROMPATH and AMFSObjectPropertySet._IMPORTEDFROM properties, respectively. Note: The AMFSObjectPropertySet._IMPORTEDFROM property value can also be configured with the server and client UseImportedFrom registry values described elsewhere in this document.

Following is an example .ini file:

[Generic]
Vault=EDM
NoHistory=0
NoSequences=1
SplitImportFrom=1

[Custom]
ChangeManagementDateCompleted=1 
ChangeManagementDateEntered=1 
ChangeManagementEnteredBy=1 
ChangeManagementPriority=1 
ChangeManagementRemarks=1 
ChangeManagementRequestType=1 
ChangeManagementStatus=1 
ChangeManagementWeekDue=1