Expose NetSuite custom fields that are not appearing¶
Introduction¶
The NetSuite connector exposes custom fields for many NetSuite objects by default.
If using private agents and custom fields are not present in schema structures for a specific object, you can add a property to the agent's NetSuite connector configuration file to expose custom fields for the object.
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 make them after each agent upgrade.
Example¶
To expose custom fields for NetSuite's SupportCase
object, for example, add the following lines (highlighted) to the netsuiteconfig.xml
file:
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 |
|
The properties needed on each line vary depending on the object. Use existing entries in the file as additional examples.
Save and close the file, then restart the agent.