Discussions
Join the NetSuite community to innovate, connect, and discover what’s next.
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Register now
Changes to Field Service Management’s Idempotency Feature
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
Regards,
@Robert Nedelkow-Oracle | NetSuite Support Community Administrator
Expand your NetSuite knowledge by joining this month's Ask A Guru Live: PROCURE TO PAY. RSVP for this event now!
