Netsuite Attribution And Field Changes

Last updated: September 16, 2025

If you notice that values are being changed on your NetSuite records even though the field in question is not mapped in your SyncSmart integration, this is likely caused by internal NetSuite scripts or automations rather than the integration itself.

Why this happens

When SyncSmart integration updates a record in NetSuite, it can trigger internal NetSuite scripts that have the ability to modify fields based on other data in the record. The integration logs may show SyncSmart as the source of the change, but this is because NetSuite attributes the field modification to the integration event that triggered the internal script.

Common causes

  • Record merging: When HubSpot records are merged, it can trigger NetSuite scripts that automatically set fields based on address or other field values

  • Internal NetSuite scripts: Custom scripts in your NetSuite instance may automatically set field values based on mapped fields like address, country, or other customer data

  • Concurrent processes: Other NetSuite processes (like order creation) happening simultaneously with the integration sync can trigger field-related automations

How to resolve this issue

There are two main approaches to prevent unwanted field changes:

Option 1: Map the desired field

The most straightforward solution is to map the desired field in your SyncSmart integration. This ensures that the integration explicitly controls the field value and prevents NetSuite scripts from overriding it.

Option 2: Review NetSuite scripts

Check your NetSuite scripts (such as User Event scripts) to identify which ones have the ability to modify fields. Look for scripts that might be triggered by integration updates and consider modifying their logic to exclude field changes when triggered by the SyncSmart integration.

Verification

To confirm that the integration itself is not changing field values:

  1. Make a test change to a mapped field (like phone number) in HubSpot

  2. Observe if the integration changes the target field (the field believed to be changed by the integration) in NetSuite

  3. If the field doesn't change during this test, it confirms the issue is caused by NetSuite scripts rather than the integration

If you continue to experience issues after mapping the field or reviewing your NetSuite scripts, contact SyncSmart support for further assistance.