Skip to Content

Expose custom fields in the NetSuite connector

The NetSuite connector exposes custom fields for many NetSuite objects by default. If custom fields for a specific object are not present in the activity schema on a private agent, you can add an entry to the agent's NetSuite connector configuration file to expose them.

Add custom fields to the configuration file

A private agent's NetSuite connector configuration file netsuiteconfig.xml is found in these default installation directories:

C:\Program Files\Jitterbit Agent\DataInterchange\xml_dtd\Schemas\Connector

/opt/jitterbit/DataInterchange/xml_dtd/Schemas/Connectors

Important

Before making changes to the NetSuite connector configuration file, be aware of these considerations:

  • Adding custom field support to an object that is already in use may cause breaking changes if you have any mappings within derived-type nodes. We recommend reviewing and reconfiguring any activities using the object to refresh schemas and remap fields as needed.

  • Any changes made to the configuration file are not applied until the agent is restarted.

  • Agent upgrades replace this configuration file. If you make changes to this file, you will need to reapply your changes after each agent upgrade.

To expose custom fields for a NetSuite object, add a <customfieldobject> entry for that object to the netsuiteconfig.xml file. For example, to expose custom fields for NetSuite's SupportCase object, add the following lines (highlighted):

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
<?xml version="1.0" encoding="UTF-8"?>
<config>
  <cachesize>
  <searchconfig>
    <customfieldtypes>
    <customfieldobjects_v2>
    <customfieldobjects>
      <customfieldobject>
        <objectName>VendorPayment</objectName>
        <getCustomizationType>transactionBodyCustomField</getCustomizationType>
        <appliesToObject>bodyVendorPayment</appliesToObject>
      </customfieldobject>
      <customfieldobject>
        <objectName>SupportCase</objectName>
        <getCustomizationType>crmCustomField</getCustomizationType>
        <appliesToObject>appliesToCase</appliesToObject>
      </customfieldobject>
      <customfieldobject>
        <objectName>Campaign</objectName>
        <getCustomizationType>crmCustomField</getCustomizationType>
        <appliesToObject>appliesToCampaign</appliesToObject>
      </customfieldobject>
      . . .
    </customfieldobjects>
    <itemsearch>
    <transactionsearch>
  </searchconfig>
</config>

The properties needed on each entry vary depending on the object. Use existing entries in the file as additional examples.

Save and close the file, then restart the agent.

Objects with more than 1,000 custom fields

If a NetSuite object has more than 1,000 custom fields and fields are still missing from the activity schema even after updating netsuiteconfig.xml, enable the Enable NetSuite Pagination option in the NetSuite connection:

  1. Open the NetSuite connection and expand Optional settings.
  2. Select Enable NetSuite Pagination.
  3. In NetSuite Pagination Limit, enter the number of custom fields to support (up to a maximum of 2000). The default value is 1000.
  4. Save and test the connection.

Note

Enable NetSuite Pagination requires agents version 11.52 or later.