Select Reference Types

A reference type enables you to map a column in an imported CSV file to a NetSuite field that can have one or more list values, such as a dropdown list or a multi-select. You specify reference types on the Import Assistant's Field Mapping page by clicking the edit icon next to a mapped field that is a dropdown list or multi-select.

Default Value or Reference Type popup.

Reference types are not available for all fields.

Possible reference types include External ID, Internal ID, Name and Script ID.

Displaying Internal IDs

You can configure NetSuite to make internal IDs available in NetSuite. During development, internal IDs help you verify that the internal ID values submitted for import match those in the existing records.

Go to Home > Set Preferences and in the Defaults section of the General tab, check the Show Internal IDs box. Lists then include the Internal ID column, as shown in the following screenshot. This change affects the current user only.

The Internal ID column highlighted.

If lists include Internal IDs, you may be able to export data from a NetSuite list page to get Internal IDs into a CSV file, because an Export to CSV button may be available from the list pages.

The assignment of internal IDs to new records is sequential. However, the sequence of internal IDs does not indicate when or in which order records were added. This is true even within specific record groups where internal IDs are unique. Therefore, you should not conclude that records with lower internal IDs were added first, whereas those with higher internal IDs were added last.

For custom applications that rely on the chronological aspect of when data was entered, you should use the Date Modified or Date Created fields, as they are guaranteed to be chronological. Additionally, for transactions with auto-generated numbers, the sequence number (for example, “tranid”) is guaranteed to be sequential based on the date transactions were entered. The internal ID of a record should never be used to determine when data was entered, and you should not build any functionality based on the sequence of internal IDs.


The user preference setting specifies the display of the internal ID, however, some records have an ID that cannot be hidden. For example, customer J Wolfe has an ID of 87 and an internal ID of 18834. The ID column cannot be removed from the customer list page.

Related Topics

Step Four Field Mapping
CSV Field Mapping Tasks
General CSV Field Mapping Tips
Required Fields on Records
Assign Default Values during Field Mapping
Assign Null Values during Field Mapping

General Notices