This notice is intended for all Active FSM Customers.
You're receiving this notification because your account uses Field Service Management (FSM). There’s an important upcoming change to how FSM stores idempotency values during sync.
What’s Changing?
When FSM version 2026.05.2 is released to production on June 16, 2026, FSM will store idempotency values in NetSuite’s native External ID field for records that FSM creates or updates during sync. FSM will no longer populate the old custom idempotency fields. You'll no longer need to create separate custom idempotency fields or add idempotency settings to the FSM configuration. Idempotency will run automatically for all mobile tabs that create new records, including custom tabs. Starting June 23, you’ll find more information about how FSM prevents duplicate records during syncs, retries, and repeated sync attempts will be available in the help topic Idempotency, SuiteAnswers ID 1021775.
Required Actions
No action is required to enable the new idempotency logic. The change will happen automatically in FSM version 2026.05.2.
Note: FSM will no longer populate the old custom idempotency fields as of version 20206.05.2 and will store idempotency values in the External ID field instead. If you have any questions, please contact NetSuite Customer Support.