The Re-Leased integration connects to NetSuite through the Re-Leased Integration Role, which is installed as part of the Re-Leased SuiteApp and pre-configured for standard NetSuite environments. If your instance includes custom fields, Custom Segments, Custom Record Types, third-party SuiteScripts, or non-standard features, the role may need additional permissions. When permissions are missing, syncs fail with an error message containing a field ID.
To identify a field from its ID: navigate to the field name in NetSuite and click Customise. The field ID is shown on that page.
Missing NetSuite Features
Some fields are only available when certain features are enabled. For example, Classifications must be enabled for classification-related fields to be accessible. Check Setup > Company > Enable Features to verify required features are active.
Custom Segments and Custom Record Types
The Re-Leased Integration Role must have explicit permissions on any Custom Segment or Custom Record Type that appears on transaction forms.
Open the Custom Segment or Custom Record Type record in NetSuite.
Navigate to the Permissions tab.
Add the Re-Leased Integration Role and grant appropriate access.
Save your changes.
Note: Custom Record Types that underlie a Custom Segment must have the Use Permissions List access type configured.
Custom Segment "Apply To" Configuration
If a Custom Segment is missing any of the following Apply To options, it will be silently excluded from the sync without returning an error. Ensure all of these are enabled:
Apply to purchase
Apply to sale
Apply as sale column
Apply as purchase column
Apply as expense column
Apply as store column
Custom Fields on Transaction Forms
Custom fields on transaction forms (such as invoices and vendor bills) must be accessible by the Re-Leased Integration Role. Under the field's Application & Sourcing settings, ensure all relevant transaction types have access — and that editing and searching are enabled, even if the field is not actively used.
Third-Party SuiteScript Fields
If a custom field or segment originates from a locked-down third-party SuiteScript, you may not be able to add the Re-Leased Integration Role to its permissions directly. In this case, exclude the field from the default transaction form used by Re-Leased by creating a dedicated form. See Understanding NetSuite Mandatory Fields and Re-Leased Sync for instructions.
Transaction Forms and the Re-Leased Integration Role
Re-Leased uses the default transaction form in NetSuite. If your default form includes unsupported mandatory fields or restricted custom fields, the sync will fail. Assign a dedicated form to the Re-Leased Integration Role that excludes these fields while preserving standard sync fields.
Custom Field Considerations
Filtered By setting — Custom fields with a Filtered By option configured are not supported. Their presence may cause sync failures.
Deselecting filtered values — Values on Filtered By fields cannot be deselected with a standard click. Use Ctrl + Click to deselect.
Troubleshooting Steps
Check the sync error message for the field ID causing the issue.
Navigate to the field in NetSuite and click Customise to confirm the field name and ID.
Verify required NetSuite features are enabled under Setup > Company > Enable Features.
Check the Permissions tab on any Custom Segment or Custom Record Type for the Re-Leased Integration Role.
Confirm Custom Record Types have the Use Permissions List access type configured.
Ensure custom fields have editing and searching enabled, with all transaction types accessible under Application & Sourcing.
For locked third-party fields, exclude them from the form used by the Re-Leased Integration Role.
Run a sync and check the Sync Results page for remaining errors.
If the issue persists, contact Re-Leased Support.