Defining Data Import preferences

Preferences determine tool behavior such as how Data Import handles duplicate records and how it resolves conflicts during an import operation. Default preferences are set in the Preference window of Data Import. They are stored locally or in the AR System Administrator Preference form (if you logged into a preference server).

When you create a mapping file (choose File > New Mapping), the preferences in the Preferences window are used by default. To change the preferences, click the Options tab in the mapping file in Data Import, and save the mapping.

To update the preferences for Data Import

1. In Data Import, choose File > Preferences.
   The Preferences dialog box appears.
   
   Data Import Preferences dialog box 
   
   

2. Set the preferences, which are defined in the following table.
   
   Data Import preferences

   Group name	Field	Function
   General	Log File	Identifies the directory and file name of the BMC Remedy Import log file, which is workspaceDir\dataimport.log by default.  Note: Only one log file is used, so each time you import data, the log file is overwritten. To keep a log file, rename it.
   	Number of Records Per Transaction	Uses transactions to import data (if the server supports transactions). For example, if you enter a value of 100, the server performs only one commit to the database every 100 records, which significantly improves performance.  Note: Specify the -b option in Data Import command line to use the bulk mode for record transfer. Bulk mode is an atomic transactional mode. If any record failed to import in bulk then Data Import rolls back the entire bulk of records.
   Duplicates	Handle Duplicate Request IDs By	Defines how to handle duplicate request IDs. The options are: Generate New ID for All Records — Assigns new request IDs to all requests in the data file, whether or not any IDs are duplicates. Generates request IDs for records that do not already have them, for example, in a CSV file created outside AR System. Reject Duplicate Records — Entries are imported using their existing IDs. If an ID is already in use, an error is generated. The error is processed according to your preferences. Generate New ID for Duplicate Records — Entries are imported using their existing IDs. If a record with the same ID already exists in the database, a new ID is generated for the imported record. Replace Old Record with New Record — Entries are imported using their existing IDs. If a duplicate ID exists, the entire database record is overwritten with the record being imported. You must map the required core fields with this option; otherwise, the server rejects the records. See Importing-data for more information about mapping. Update Old Record with New Record's Data — Entries are imported using their existing IDs. If a duplicate ID exists, only the fields being imported are replaced, merging the record. This setting also automatically makes all non-core required fields optional. See Data handling for more information about preferences related to required fields.
   	If Multiple Requests Match	Defines what happens when multiple requests match. The options are: Skip Record — Skips the record in the data file and does not import anything for that record. Use First Matching Request — Updates the first request with the data from the data file. Update All Requests — Updates all the requests with the one from the data file.
   Data Handling	Make Non-Core Required Fields Optional *	Specifies that noncore required fields are optional during the import. By default, the check box is cleared, and all required fields are treated as required. If a required field has a NULL value, an error is generated. The error is processed according to what you enter in the Bad Records field under the "Error Handling" section.
   	Disable Pattern Matching *	Specifies that records are imported, even if the data in a field does not match the specified pattern. By default, the check box is cleared, and the server rejects records if data in the field does not match the specified pattern. The error is processed according to what you enter in the Bad Records field under the "Error Handling" section.
   	Suppress Filters	Suppresses (turns off) any filters that execute on Merge.
   	Suppress Field Default Values	Suppresses the default values of the fields. If the field has a default value and the data you are importing for the field is empty, the import process does not use the default value for that field.
   	Remove Leading Spaces and Tabs *	Specifies that all leading white space is removed from each field imported. By default, the check box is cleared, and values are imported exactly as they appear in the data file.
   	Remove Trailing Spaces and Tabs *	Specifies that all trailing white space is removed from each field imported. By default, the check box is cleared, and values are imported exactly as they appear in the data file.
   	Truncate Strings Exceeding Field Limit *	Specifies that fields that are too long are truncated. By default, the check box is cleared, and fields whose contents are too long generate an error. The error is processed according to what you enter in the Bad Records field under the "Error Handling" section.
   	Import Records with Too Few Fields	Specifies how BMC Remedy AR System imports records that contain fewer fields than described by the field titles in the data file. Problem records are imported with NULL values in the missing fields. By default, the check box is cleared, and the problem records are not imported and an error is generated. The error is processed according to what you enter in the Bad Records field under the "Error Handling" section.
   	Import Records with Too Many Fields	Specifies how BMC Remedy AR System imports records that contain more fields than described by the field titles in the data file. By default, this option is selected. The problem records are imported, and the extra fields are ignored. If you clear the check box, the problem records are not imported, and an error is generated. The error is processed according to what you enter in the Bad Records field under the "Error Handling" section.
   Date Format	Short Date Format	Defines the short-date format. The options are: M/d/yy d/M/yy yy/M/d The component order is based on the Locale settings as defined by Oracle Java. Note: When you import data containing the date fields using the Data Import tool, you must select the same format under User Preferences for the Date Format related fields that you have used in the data file to import the date related data in the correct format.
   	Short Date Separator	Defines the separator character between the month, day, and year. Slash ✅️ is the default. You can use any character that is not part of the field separator string for the data file.
   	Long Date Format	Defines the long-date format. The options are: dddd, MMMM d, yyyy dddd, d MMMM, yyyy dddd, yyyy MMMM d The component order is based on the Locale settings as defined by Java. Note: When you import data containing the date fields using the Data Import tool, you must select the same format under User Preferences for the Date Format related fields that you have used in the data file to import the date related data in the correct format.
   Time Format	Hour Mode	Defines the hour mode. The options are: 12 Hour — Tracks in the 12-hour clock (default). 24 Hour — Tracks in universal time.
   	Separator (Time Format)	Defines the time format separator between the hours, minutes, and seconds. A colon (:) is the default. You can use any character that is not part of the field separator string for the data file. Note: When you import data containing the time fields using the Data Import tool, you must select the same format under User Preferences for the Time Format related fields that you have used in the data file to import the time related data in the correct format.
   	AM/PM Position	Specifies where the symbol is positioned if you select 12 Hour for the Hour Mode. The options are: Prefix — The symbol is positioned before the time string (for example, AM 10:23:47). Suffix (default) — The symbol is positioned after the time string (for example, 10:23:47 AM).
   	AM Symbol	Defines the symbol that indicate mornings if you select 12 Hour for the Hour Mode.
   	PM Symbol	Defines the symbol that indicates afternoon if you select 12 Hour for the Hour Mode.
   Real Number Handling	Digit Group Separator	Defines the separator for groups of real numbers in .arm and .armx files.
   	Decimal Separator	Defines the decimal separator for real numbers in .arm and .armx files.
   Error Handling	Bad Records	Defines what happens when the import process encounters a bad record. The options are: Alert User with Popup Dialog — Interrupts the import and displays an error message (default). The message contains these choices: Yes — Skips the problem record, writes the error and the record data to the import log, and continues to import remaining records. Yes to All — Skips all problem records that generate the same error, writes the error and the records to the import log, and continues to import remaining records. Stop Import — Stops the import and prompts you to copy all remaining data to the import log. Skip Bad Records — Skips problem records without displaying an error message, and continues with the import. Try Fallback Mapping Before Alerting User — If a mapping generates an error, BMC Remedy Import uses the fallback mapping specified in the Fallback Mapping preferences. If the fallback mapping also generates an error, a message is displayed. The error is generated against the original mapping error. Errors are not generated against fallback mappings.

   * These settings are affected by field attributes set when fields are defined. See Fields-overview and Creating-and-managing-fields.