Skip to main content

FAQ: Customizing ExtendInsights for Data Management NetSuite to modify default settings

ExtendInsights Data Management | Override default settings such as batch sizes and warning behavior

Updated today

ExtendInsights for Data Management (NetSuite) allows administrators to customize global default settings that control how data operations behave. These settings can help optimize performance, enforce stricter validation, or work around NetSuite API limitations.

This article explains what can be customized, how the settings work, and when to adjust them.


โš ๏ธ Important Scope and Impact

All settings described in this article are:

  • Global

  • Applied to all ExtendInsights for Data Management users

  • Effective immediately after being saved

Changes should be reviewed carefully and tested in Sandbox before applying to Production.


Prerequisites

Before modifying any settings:

  • A NetSuite Administrator must install the CloudExtend Excel Data Management for NetSuite bundle

  • Learn how to install the bundle here

If you previously created custom settings

If your team created custom records at the direction of Celigo Support before installing the bundle, ensure your NetSuite Admin has followed the cleanup and migration steps outlined in the setup instructions before continuing.


๐ŸŽฅ Accompanying Video

We recommend watching the accompanying video before making changes to understand how these settings affect ExtendInsights behavior.


Understanding Batch Sizes

Many ExtendInsights operations process records in batches.

What is a batch size?

A batch size defines how many records are sent between Excel and NetSuite in a single operation.

Example:
If you delete 600 records and deleteBatchSize is set to 100:

  • ExtendInsights processes 6 batches of 100 records

  • NetSuite processes each batch sequentially and returns results before the next batch begins


โš ๏ธ Batch Size Considerations

Increasing batch sizes:

  • May improve speed in some environments

  • Can also cause timeouts or failures if NetSuite cannot process the larger batch within its limits

๐Ÿ’ก Recommendation:
Increase batch sizes cautiously and test changes in Sandbox.


Custom Settings You Can Modify

The following settings are available in the ExtendInsights configuration record.

Setting

Default Value

Description

deleteBatchSize

100

Number of records processed per delete operation

downloadPageSize

25

Number of records returned per page during downloads

refreshBatchSize

25

Number of records processed during refresh

uploadBatchSize

50

Number of records processed per upload batch

treatWarningsAsErrors

false

Controls whether NetSuite warnings block record creation or updates


Treat Warnings as Errors

By default:

  • NetSuite warnings (e.g., Vendor Credit Limit Exceeded)

  • Allow the record to be saved

  • Display a yellow warning in the Reserved column

When treatWarningsAsErrors is set to true:

  • The record is not saved

  • ExtendInsights returns a red error message

  • Users must resolve the issue before retrying

This setting is useful when warnings should prevent data changes.


How to Modify Batch Size Settings

Your NetSuite Administrator must update the configuration record.

  1. In NetSuite, use Global Search to find:
    โ€‹Celigo CENS Batch Size Setting Record

  2. Open the record.

  3. (Recommended) Customize the list view to include the Value column and enable inline editing.

  4. Update the desired setting (for example, uploadBatchSize).

  5. Save the record.
    โ€‹

Changes take effect immediately.


Advanced: Custom Metadata to Work Around NetSuite API Limitations

ExtendInsights uses a custom metadata record to work around known NetSuite API limitations:

Custom Record ID:
โ€‹customrecord_celigo_smartclient_meta

1. Picklist Search Workarounds

Use this record when:

  • A picklist field is read-only in the userโ€™s form

  • NetSuite API does not return available values

  • You still need the values for filtering or selection

2. Custom Segment Metadata

NetSuite APIs do not always expose custom segment metadata.
This record allows ExtendInsights to retrieve:

  • Segment values

  • Relationships

  • Dependencies

3. Custom Field Dependencies

If a field depends on another field (standard, custom, or segment):

  • Dependency metadata can be defined here

  • ExtendInsights uses this metadata during template building and validation


Need Help with Metadata Configuration?

Defining custom metadata records requires careful setup.

If you encounter NetSuite API limitations or need help defining metadata:

๐Ÿ“Ž Include the field or segment details and the use case youโ€™re trying to support.

Did this answer your question?