Managing Fields in NetSuite Connector for Integrations

The management of fields in NetSuite Connector is crucial to ensure that updates in your NetSuite account reflect accurately within the Connector. Neglecting to manage field changes can lead to broken mappings or configurations, which may disrupt the integration between your marketplace or cart and NetSuite.

What Happens When a Field is Deleted?

If you delete a field in your NetSuite account or within your marketplace/cart, it’s essential to verify that this field is not included in your NetSuite Connector mappings. Failing to do so will result in a failure of the mapping. For example, if you remove the field custbody_fa_channel_order from NetSuite, the Connector will not be able to post the corresponding Order ID from your marketplace/cart. Consequently, the mapping will break.

How to Fix Broken Mappings

To resolve mapping issues arising from field deletions, you have a couple of options:

• Restore the Deleted Field: If feasible, you can simply restore the deleted field to ensure continuity in your mappings.
• Update Mappings with New Fields: Alternatively, you can replace the deleted field by updating your mappings with an existing field from the corresponding endpoint.

By proactively managing your fields and ensuring they are properly mapped, you can maintain the integrity of your NetSuite Connector operations, thus optimizing data flow and minimizing disruptions.

Best Practices

• Regularly review and update mappings, especially after making changes to fields in your systems.
• Document field usages within NetSuite Connector to assist in identifying any potential impacts from deletions.

Source: This article is based on Oracle's official NetSuite documentation.