Assign Default Values during Field Mapping
The Import Assistant automatically populates some dependent field values when related field values are set, in the same manner that many dependent field values are automatically populated in the user interface.
In addition, it is possible to assign default values for required fields on the Import Assistant's Field Mapping page. A default provides a consistent value for a record reference field across all imported records. For example, the simplest thing to do when you import new lead records would be to set a default value for the lead status column to “LEAD-New”.
To provide a default value for a field on the Field Mapping page
-
Click the edit icon in its row to open a popup.
-
Choose Provide Default Value, and select a value from the dropdown or popup list.
Note:Whether the list of available values is a dropdown or popup list depends on the number of values and your setting for Maximum Entries in Dropdowns at Home > Set Preferences.
Be aware that even if you set a default value for one or more fields in a sublist, no sublist data is imported unless you map at least one field for that sublist. For more information about working with sublists, see Sublist Data Import.
Using Dependent Field Values as Defaults
When you click the edit icon for a dependent field, meaning a field with available values that vary according to the value selected for another field, the list does not filter values in the same manner that they are filtered in the user interface. These cases are most likely to occur in OneWorld accounts, for fields that are dependent on subsidiary values.
For example, in a OneWorld account, available tax code values for a transaction item vary according to the customer, and to the customer's associated subsidiary. In the user interface, the Tax Code field dropdown list filters the listed tax codes to only those that are valid. In the Import Assistant, the Default Value field lists all tax codes without any filtering.
Consider default values for dependent fields carefully. Because the Default Value does not filter the values for these fields, you may inadvertently select an invalid value. For example, you could select a tax code value that is not valid for some of the customers or subsidiaries listed in your CSV file. This type of invalid value can cause validation errors when you attempt to complete the Field Mapping step.
If a dependent field is not required, you have the option of entering values in the user interface after the import is complete.
Assign a Default Value for the Primary Sales Rep Field
For Customer, Lead, or Prospect records added through CSV import, values for Primary Sales Rep do not default to be the user performing the import, so the Field Mapping page is a good place to specify a default value for this field. This behavior differs from the NetSuite user interface, where the user entering data on the form is the default for Primary Sales Rep.