Idempotency in Field Service Management

Idempotency in NetSuite's Field Service Management (FSM) mobile app is crucial for maintaining data accuracy during unreliable network conditions. It ensures that only a single record is processed per unique action, preventing duplicates from repeated sync attempts or unstable connections.

How Does Idempotency Work in FSM?

The idempotency feature ensures that when mobile users operate in areas with erratic connectivity, any resubmitted requests due to interrupted syncs are processed only once. Normally, retries can lead to duplicate records, but idempotency eliminates this issue by associating a unique key with each action.

By default, idempotency runs on standard mobile tabs, including Asset, Sales Order, Inventory, Time, Expenses, Files, Notes, Task, Quote, Order, and Return. Custom tabs also require idempotency keys setup to avoid duplicate records.

How to Set Up Idempotency for Custom Tabs?

For custom records, you'll need to manually add an idempotency field if it doesn't already exist. Here's how:

1. Navigate to Customization > Lists, Records, & Fields > Record Types.
2. Select the custom record type.
3. Go to the Fields subtab and create a New Field.
4. Define the field with a descriptive label and an ID using _idem as a suffix (e.g., custrecord_nx_abc_idem).
5. Choose Free-Form Text as the type and ensure Store Value is selected.
6. Save the new field.

Configuring Idempotency in FSM

1. Go to Field Service > Administration > Configuration.
2. In the JSON field, define idempotency for custom records by specifying the idempotencyField property with your custom field ID.
3. Repeat for each applicable tab, then save.

Note: It's advisable to exclude the idempotency field from appearing in the mobile app using the exclude property.

Who This Affects

• Developers and Administrators: involved in setting up and maintaining FSM configurations.
• Field Service Operatives: who rely on mobile apps in areas with unstable network conditions.

Key Takeaways

• Idempotency prevents duplicate records in FSM during repeated syncs.
• It's automatically applied to standard tabs but must be configured for custom records.
• Developers need to define an idempotency field and its configuration for custom tabs.