Configuring FSM Mobile Duplicate Creation Protection
You don't need additional configuration for duplicate creation protection in FSM Mobile. It applies to standard record creation, including additional custom-record resources that use FSM's standard record synchronization.
For previous configuration settings, see Deprecated Configuration.
FSM uses the native NetSuite External ID field (externalid) to recognize a record created by an earlier request. FSM can fail to recognize repeated creation requests if custom save processing bypasses the External ID mechanism or FSM's External ID value changes.
No separate custom idempotency fields, field mappings, or resource-specific idempotency settings are required for standard record synchronization.
Deprecated Configuration
The previous idempotencyField setting and custom idempotency-field mappings are unnecessary for standard FSM Mobile record synchronization.