ExtendInsights for Data Management supports NetSuite custom segments. Most issues are caused by one of the following:

The custom segment is not applied to the record type (NetSuite configuration)
The user role does not have permission to view/set the segment
ExtendInsights needs a metadata or picklist refresh
The segment was mapped at the wrong level (header vs line)

This guide helps you identify the root cause and resolve it quickly.

Quick Answer

Yes, custom segments are supported.
If you can’t see a custom segment in the template builder, it is usually a NetSuite setup or metadata refresh issue.
If you can see it but uploads fail or don’t save, it is usually a permissions issue or a header/line mapping issue.

Start Here: What problem are you seeing?

I can’t find the custom segment in the template builder
➡️ Go to: Segment Not Visible
I can see the segment, but picklist values are missing
➡️ Go to: Picklist Values Missing
Upload succeeds, but the value doesn’t save in NetSuite
➡️ Go to: Value Doesn’t Save (No Error)
Upload fails with an error on the segment column
➡️ Go to: Upload Error on Segment Column

Segment Not Visible in the Template Builder

Step 1: Confirm the segment exists and get its ID

In NetSuite:

Go to Customization > Lists > Custom Segments
Locate your segment and note the ID (for example: cseg_const_category)

➡️ See how to identify custom segment ID

Step 2: Confirm the segment is applied to the right record type

Custom segments must be enabled for specific record types.

In NetSuite:

Open the custom segment definition
Go to Application & Sourcing
Confirm the segment is enabled for the record type you are working with (Vendor Bill, Journal Entry, etc.)

➡️ Check if the custom field has been applied to forms

Step 3: Confirm it is exposed on the form (recommended)

If a segment is not exposed on the form (or not available to the role), it may not be usable as expected.

Step 4: Confirm role permissions

If users can’t see any custom fields/segments, it may be role permissions. Typical permissions that help with visibility include custom fields/record-related permissions, depending on your setup.

➡️ Check user permissions if Custom Segments were added

Step 5: Refresh metadata in ExtendInsights

If the segment was recently added or updated, refresh metadata in ExtendInsights.

➡️ Follow: How to Refresh Metadata in ExtendInsights

If it still doesn’t appear after refresh, use the manual mapping steps in Advanced: Manual Mapping.

Picklist Values Missing

ExtendInsights caches picklist values for performance. If new segment values were added in NetSuite, the picklist may need a refresh.

Step 1: Refresh picklist values

Click a cell mapped to the custom segment (in your template)
Open Cell Operations
Click the three dots (...)
Select Refresh

Step 2: If still missing, refresh metadata

➡️ Follow: How to Refresh Metadata in ExtendInsights

Value Doesn’t Save (No Error)

If the upload completes but the custom segment value doesn’t show in NetSuite, the most common cause is that the segment is mapped to the wrong level.

Step 1: Confirm whether the segment is Header-level or Line-level

Custom segments can be configured to apply to:

Header only
Lines only (Item lines and/or Expense lines)
Both

Confirm where it is applied in the segment’s NetSuite setup (Application & Sourcing).

Step 2: Use the correct mapping path (Vendor Bill examples)

Use the correct mapping depending on where you need the segment:

Segment Location	Where it appears in NetSuite	Mapping path example
Header	Vendor Bill header	`VendorBill.customFieldList.cseg_const_category`
Expense line	Vendor Bill > Expenses sublist	`VendorBill.expenseList.expense.customFieldList.cseg_const_category`
Item line	Vendor Bill > Items sublist	`VendorBill.itemList.item.customFieldList.cseg_const_category`

Step 3: Use Internal IDs for the segment value (recommended)

If the segment value resolution is inconsistent (name mismatch, duplicates, etc.), enter the internal ID using this format:

[[1234]]

NetSuite will recognize the correct value behind the scenes.

Upload Error on Segment Column

If the segment column returns an error, check these common causes:

Checklist

The value is not valid for that segment
The user role cannot set the segment
The segment is mandatory on the form and left blank
The mapping is incorrect (wrong header vs line mapping)
The value needs to be entered as an internal ID: [[1234]]

If the error message indicates “invalid reference” or “invalid field value,” the value is typically not resolvable (use picklist selection or internal ID format).

How to identify the Custom Segment ID

Step 1: To locate the segment ID

In NetSuite, go to Customization > Lists > Custom Segments
Look for the segment’s ID value (example: cseg_const_category)

This ID is what you reference in your mapping path.

Step 2: Determine if the Custom Segment is at the header or the line level

An example of a custom segment named cseg_const_category at the header level and line level:

Custom Segment Location	Sub-level	Custom Segment Line Level
Header Level	NA	`=T(N("VendorBill.customFieldList.cseg_const_category"&4))`
Line Level	Expense Tab	`=T(N("VendorBill.expenseList.expense.customFieldList.cseg_const_category"&4))`
Line Level	Items Tab	`=T(N("VendorBill.itemList.item.customFieldList.cseg_const_category"&4))`