Content Manager 25.2 DataPort Help

# Importing Locations

To import Locations into Content Manager using Content Manager DataPort:

General

1. Start DataPort from the Content Manager client, on the Administration ribbon, in the Other group, click Import/Export. Alternatively, from the Content Manager install path, open the TRIMDataPortConfig application.

   The Content Manager DataPort - New Project dialog box appears.

2. Type the name of the project in the Project Name field.
3. Type a description of the project if required.
4. Select the Authentication Method to use. From the drop-down list, select from:
   - Active Directory Federated Services
   - Explicit Windows Authentication
   - Google Apps
   - Integrated Windows Authentication

   CAUTION: If anything other than Integrated Windows Authentication is used then DataPort will not run in an unattended fashion, a user name and password will be required.

5. Select the Content Manager Database the Locations are to be imported into by selecting the dataset name from the recently used drop-down list or use the KwikSelect to select the database from the list of available databases.
6. From the drop-down list, select Import as the Data Direction.
7. From the drop-down list, select Location as the Content Manager Object Type.
8. From the drop-down list, select the File Format. By default, Tab Delimited is selected.
9. Browse to, or use the drop-down list to select, the location of the Import File Path.
10. From the drop-down list, select Yes or No to Show Progress Window.
11. From the drop-down list, select Yes or No to Update on Duplicate. If Yes is selected, then if a duplicate Location is found during the import process it's metadata will be updated to match that in the import file.

Settings

1. From the drop-down list, select Yes or No to Use Bulk Loader when importing Locations. If Yes is selected, a Warning is displayed:
   Warning. When running an importing using Bulk Loader import mode a number of features are disabled. Records may be numbered according to the special bulk loader sequence and some expensive integrity checks will be bypassed and no audit trail is created.

NOTE: If Yes is selected a new Record Type will be created in the Content Manager dataset the Locations are being imported into. This Record Type will be called DataPort Default. As this Record Type is not used by any other Content Manager processes it can be deleted from the dataset once the import has been completed. This behavior is due to the BulkLoader functionality requiring an Origin object in order to track it's use and Origin objects requiring a Record Type.

See Origins and BulkLoader for additional information about using the BulkLoader.

1. From the drop-down list, select Yes or No to Relax Business Rules for Conversion. If Yes is selected then checks on Location interdependent properties are not done during the import process.
2. From the drop-down list, select Yes or No to Relax Business Rules for Performance.

   NOTE: Duplicate Locations will not be created if this option is selected due to CM DataPort duplicate checking, secondary internal checks are being bypassed during the import process which can improve performance.

3. From the drop-down list, select the Location Match Type. Select from:
   - Matches must be unique
   - Must match - never create new Location
   - Never match - always create new
   - Use first match

See Location Match Type Behaviors for how these options behave.

1. From the drop-down list, select the Property to use to uniquely identify a location. Select from:
   - Email Address
   - ID Number
   - Name
   - Unique Identifier
   - Unique Name

When matching imported data to existing Locations this property will be used. Once this property is selected it still must be added to the Field Map to enable the data in the import file to be mapped to the data in Content Manager.

Field Map

15. Map the fields/items to be imported.

- Target Properties - these are the fields/items available in the Content Manager database.
- Source Fields - these are the fields/items that are available in the Import file.

1. To map all matching items, click Map All Matching Pairs. This automatically selects all items with the same caption and adds it to the Mapped Items section.

To map individual fields/items, select the Target Properties item and then select the matching item in the from the listed Source Fields, click Map Pair. The pair will be added to the Mapped Items section.

1. Click Save. Type the name of the Import DataPort Project file, click Save.
2. Click Execute to run the project.

If Show Progress Window is set to Yes, the Content Manager DataPort Engine will be displayed to show the progress of the Import. If it's set to No, the Import will run in the background. The Content Manager DataPort Engine can be accessed from the System Tray/ Notifications bar.

TIP: A log file is generated for each Import, this can be accessed by clicking the Logs menu on the Content Manager Engine window.

NOTE: When importing Locations of a Storage Provider type, the Administered By Locations must be existing Locations in the Content Manager dataset the Storage Provider Locations are being imported to.

NOTE: When importing Locations, if a Location Type is not mapped but a Date of Birth is then the imported Location will be created as a Person type. This is due the Date of Birth property only being supported on Person Location types in Content Manager.

Copyright 2008-2025 Open Text
Version 25.2 | Last updated July 2023
Contact

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to hprmdocumentation@microfocus.com.

We appreciate your feedback!

Product: Content Manager 25.2

Topic Title: Importing Locations