Importing Data Into Your Database → Importing Data From Another SBM Database → Specifying Additional Import Options for SBM Data Imports
When you import data from another SBM database, the Additional Data Options dialog box enables you to set options for re-importing data, importing change history, notes, files attachments, and version control actions for each item, and re-establishing subtask relationships for each item imported with this option set.
Consider the following information when you select additional import options:
Some import options, such as importing a large number of file attachments, may take considerable time. To improve performance, you may want to separate additional import options into multiple Import Option Sets and import them after importing items and other associated data such as selections and users.
The update options apply to imported data as well as notes, change history, file attachments, version control actions, and subtask relationships.
For best results, establish a user map for your receiving database before importing notes, attachments, change history, version control actions, and subtask relationships. This helps the Import Data Wizard recognize users accurately at the beginning of the import. For details, refer to Mapping SBM Source Fields to Destination Fields.
The following options are available:
Write Over Data in the Item, Using Import Data Maps – Select this option to write over data in previously imported items. For example, you may want to write over previously imported items if you adjust your field mapping after your initial import. During the subsequent import, field values are adjusted for previously imported items based on the new values, and new items are added.
Leave the Item Unmodified – Select this option to import new data without modifying previously imported data. This option is selected by default.
New Records Must Have Unique Text in Field – To prevent duplicate records in the receiving database, select this check box, and then select a field from the list. The list contains Text fields in receiving database that are not set as Memo fields and that were mapped on the Map External Source Fields to Destination Fields dialog box. Before adding new records, the Import Data Wizard checks the receiving table for records with identical values in this field. Searching is case-insensitive. Matching records are not updated, and new records containing the same value are not created. When new records are not created because of this setting, entries are added to the log file.
Consider the following information when you select a field for uniqueness checking:
The system "title" field in the receiving table is marked with an asterisk.
To guarantee unique item IDs for all items imported to a table, you can select the Item Id field for uniqueness checking. Doing so overrides numbering properties you may have set up in the receiving project, however.
To avoid problems with duplicate contact names when you import data into the Contacts table, consider mapping the e-mail field and using it for uniqueness checking.
Import Change History for Each Imported Item – Select this option to import change history for all items imported with this option set, based on mapped source fields. This option is selected by default.
Change history is imported on a field-by-field basis and is not imported for fields that are not mapped.
If you mapped fields of different types (for example, a Single Selection field to a Text field), change history values may display as "none" or have incorrect values for that type of field.
For fields of the same type, the Import Data Wizard converts each old value, new value, and user in three steps. First, mapped values and users for an Import Option Set are converted. Second, values and users established during an import are converted. Third, values and users established during a previous import from the same source database are converted. If these methods fail, the change history item is set to "none."
Change history is not created for notes and attachments added during import.
When you update previously imported items, change history for mapped fields is replaced with change history from source item fields.
Import Notes for Each Imported Item – Select this option to import notes and e-mail messages attached to items in the source database. This option is selected by default.
Import File Attachments for Each Imported Item – Select this option to import files attached to items in the source database. To import file attachments, they must be stored in the source SBM database and not on a file system. Imported file attachments are stored depending on settings in the receiving database. For details on storing attachments, refer to Setting Attachment Options. In addition, URLs and files attached to items are imported when this option is selected; item links are not. This option is selected by default.
Import Version Control Actions Made Against Each Imported Item – Select this option to import version control actions associated with items in the source database. This option is selected by default, but is disabled if you are importing to an auxiliary table.
Establish New Contact Records for New Users Created Through This Import – Select this check box to create new records in the Contacts table for imported users. This option is selected by default, but is disabled if you are importing data into the Contacts table.
After specifying additional import options, click Next to continue.
The Save Your Import Option Set dialog box opens. For details, refer to Saving Your Import Option Set. For details on executing Import Options Sets, refer to Executing Import Options Sets. For logging information, refer to Import Data Log Information.
Copyright © 2001–2018 Serena Software, Inc., a Micro Focus company. All rights reserved.