NetSuite regularly introduces new standard fields as part of its biannual releases. In some cases, these new fields appear in the NetSuite UI but are not immediately available in ExtendInsights templates.

This article explains why this happens and provides a supported workaround using NetSuite custom fields and workflows so you can continue working with those fields in ExtendInsights.

🎥 Video Walkthrough

You can watch the walkthrough video below or follow the written steps in this guide.

See the video below or read on for details

Why can't I see these new fields on ExtendInsights?

ExtendInsights for Data Management communicates with NetSuite using SOAP Web Services.

In some cases:

NetSuite displays new standard fields in the UI
But those fields are not exposed via the SOAP API
As a result, ExtendInsights cannot list them in the template builder

This is a NetSuite API limitation, not a permission or ExtendInsights issue..

Good News: There Is a Supported Workaround

Even when a standard field is not exposed via the API, you can still work with it in ExtendInsights by using:

A custom field (as a proxy)
A NetSuite workflow
A workflow action to map values from the custom field to the standard field

This approach is fully supported and commonly used.

How the Workaround Works (High Level)

Create a custom field that mirrors the missing standard field
Create a workflow on the record type
Add a Set Field Value action that copies the custom field value into the standard field
Use the custom field in your ExtendInsights template

ExtendInsights writes to the custom field → NetSuite workflow moves the value to the standard field.

Workaround Details (Example Used in This Guide)

For demonstration purposes, this guide uses:

Record Type: Inventory Item
Missing Standard Field: Vendor Return Variance Account

You can apply the same approach to other record types and fields by substituting your own values.

Step 1: Create a Custom Field (Proxy Field)

You'll need to create a new custom field that will temporarily be used to mimic the standard field not available via the API.

In NetSuite, go to:
Customization → Lists, Records, & Fields → Item Fields → New
Configure the custom field:
- Label: Custom Vendor Variance Account (example, put any name you prefer)
- Type: List/Record
- List/Record: Account
- Applies To: Inventory Item (or your target record type)
Save the custom field.

This field will be visible in ExtendInsights and used in your template.

Step 2: Create a NetSuite Workflow

Now that your custom field has been created, the next step is to create a NetSuite workflow that will map the values from the custom field to the standard "Vendor Return Variance Account field.

Go to:
Customization → Workflow → Workflows → New
Configure the workflow:
- (1) Name: Item Vendor Variance Account Custom (example, put any name you prefer)
- (2) Record Type: Item (Choose the Record type you are working on)
- (3) Sub Type: Inventory Part
- (4) Initiation: Event Based (Select this initiation to tell when the workflow will run)
- (5) Event Definition: On Create and On View or Update
- (6) Trigger Type: Before Record Submit
- (7) Event Types: Create and Edit
- (8) Contexts:
  - User Interface (Optional. Add if you want this to also work in the NetSuite UI)
  - SOAP Web Services (Required)
  (9) Release Status: Testing (change to Released after validation)
Save the workflow.

Step 3: Add a Workflow Action

Once we create the workflow, we are going to add an Action to the workflow, so the value will map from the custom field to the standard "Vendor Return Variance Account field.

By default, the newly created workflow will have a State. We can double-click on the state to edit and give it a name.

Open the workflow state (double-click the default state).
Click New Action → Set Field Value.
Configure the action:
- (1) Trigger On: Before Record Submit
- (2) Event Types: Create and Edit
- (3) Contexts:
  - User Interface (Optional. Add if you want this to also work in the NetSuite UI)
  - SOAP Web Services (Required)
- (4) Field: Vendor Return Variance Account (standard field, you may select preferred field)
- (5) Select From Record: Current Record
- (6) Select From Field: Custom Vendor Variance Account (custom field, you may select preferred field)
Save the workflow.

Step 4: Use the Custom Field in ExtendInsights

Open ExtendInsights for Data Management.
Add the custom field to your template.
Load the template into Excel.
Enter values into the custom field column.
Upload or create the record.

Step 5: Validate the Result

After upload:

Open the record in the NetSuite UI.
Confirm the standard field (Vendor Return Variance Account) is populated.
The value should match what was entered in the custom field via ExtendInsights.

⚠️ Important Notes & Best Practices

The workflow must include SOAP Web Services context for ExtendInsights to trigger it
Always test workflows in Sandbox before releasing to Production (If sandbox is available)
Keep workflows in Testing until validation is complete
Document proxy fields so users know which fields are ExtendInsights-only