Prerequisite
The below-mentioned customizations require that your NetSuite Admin install the ExtendInsights Excel bundle into your NetSuite Account. Learn how here.
If you have previously installed created your own custom record at the advice of our support team please ensure your NetSuite Admin has followed the instructions here before installing the bundle.
Accompanying video
Once the bundle has been installed you will be able to tweak the settings described below. Please note these settings are global and will affect all ExtendInsights for Data Management NetSuite users.
Since most settings have a batch size you should have an understanding of what that means.
Batch size is the number of records sent to or from Excel to NetSuite for each operation. For example, if you had 600 records to delete and a deleteBatchSize set to 100 there would be 6 batches of 100 each sent to NetSuite. NetSuite processes the 1st 100 and returns results to Excel which then pushes the next batch of 100.
Increasing values beyond the default settings may cause issues such as time-out errors. For example, if the batch size is increased but NetSuite is unable to process the increased amount of data within a certain time frame it will return a time-out error.
Custom settings available for tweaking
deleteBatchSize
Default value 100downloadPageSize
Default value 25refreshBatchSize
Default value 25uploadBatchSize
Default value 50treatWarningsAsErrors
Default value false
When ExtendInsights encounters a Warning from NetSuite (such as Vendor Credit Limit exceeded) it could allow the record to be saved or rejected. By default, ExtendInsights will save the record and return a warning in yellow text in the Reserved Column. Change the default value to true to prevent the record from being saved. Error messages describing the reason it could not be saved would appear in the Reserved Column.
Modifying the data operations batch sizes for ExtendInsights for Data Management NetSuite
Your NetSuite Admin will need to locate the Celigo CENS Batch size Setting Record (installed by the bundle) and list the values (we suggest you tweak the default view to include value and enable inline editing).
Example: The arrow below shows where to change the uploadBatchSize.
Using custom metadata setting the record to workaround NetSuite API limitations
ExtendInsights uses this custom metadata record customrecord_celigo_smartclient_meta to workaround medata data limitations of NetSuite API. Following are a few cases where customers can benefit from these custom records.
Apply a search workaround for a picklist field whose values we are unable to get via NetSuite API calls because of its read-only or NS limitation. Ex: If a field is read-only in the user's default form and they want to see values for it in the filter page.
Defining metadata for custom segments: NetSuite API is yet to include the custom segments metadata in the response, we define the metadata in this custom record so that ExtendInsights can pull it from this custom record.
Custom fields dependencies: If a custom field is dependent on another custom field/standard field (or a custom segment dependent on another custom segment) metadata can be defined in these custom records and NetSuite does not provide this information via Web Services.
Contact Celigo Support below (use chat below or email cloudextend-support@celigo.com) if you run into these issue API limitations and we will help you define these custom records with the proper metadata.