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:

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

Configuring Idempotency in FSM

Go to Field Service > Administration > Configuration.
In the JSON field, define idempotency for custom records by specifying the idempotencyField property with your custom field ID.
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.

Frequently Asked Questions (4)

Does idempotency in FSM apply to both standard mobile tabs and custom tabs?

Idempotency is automatically applied to standard mobile tabs in FSM but needs to be configured for custom tabs. Custom tabs require a unique idempotency field to prevent duplicate records.

What permissions are required to set up idempotency for custom records?

To set up idempotency for custom records, users need appropriate permissions to access and modify record types in the customization settings. This typically includes permissions for customization and record editing.

How does idempotency interact with existing sync tasks in FSM?

Idempotency prevents duplicate records during sync retries by ensuring that each unique action is processed only once, even if there are connection interruptions. This avoids issues that typically arise with duplicate entries during sync tasks.

Will implementing idempotency affect existing workflows in NetSuite?

Implementing idempotency should not affect existing workflows directly, but it's essential to review any custom records and their configurations to ensure the new idempotency fields are properly integrated without causing conflicts.