FSM Mobile: Text Field Cursor Fix and Duplicate Entry Elimination
Patch 2025.10.6 resolves two FSM mobile bugs: cursor jumping and lag in text fields, and duplicate inventory/time entries appearing after app refresh or reopen.
What changed
This is a bug-fix patch (2025.10.6) targeting the Field Service Management (FSM) mobile application. No new APIs, records, or scripting surfaces are introduced.
1. Reliable Text Entry in Mobile Text Fields
The cursor in mobile text input fields previously jumped to the end of the string during typing, causing lag and intermittent character deletion. The patch stabilizes cursor position so text entry behaves as expected.
2. No More Duplicate Entries After App Refresh or Reopen
Adding inventory items or time entries in FSM mobile could result in duplicates appearing in the inventory or time tabs when the page was refreshed or the app was reopened. The patch ensures each entry is rendered exactly once regardless of app lifecycle events.
Technical notes
Oracle provides no detail on which internal components were patched. Both fixes are client-side within the FSM mobile app. There is no indication of changes to underlying records (inventoryitem, timebill), SuiteScript APIs, REST/SOAP endpoints, or SuiteFlow/workflow behavior. If you have custom client scripts or user event scripts that fire on these record types within FSM contexts, they are unlikely to be affected, but verify in your Sandbox after the patch rolls out.
What to do
- No migration or code changes required.
- If you have filed support cases for either of these FSM mobile issues, confirm the fix in your environment after the patch is applied.
- If you built client-side workarounds (e.g., custom debounce logic for text fields, or deduplication scripts on list views), consider removing them to avoid conflicts with the native fix.
- Test FSM mobile workflows in your Sandbox — particularly inventory receipt and time entry — to confirm expected behavior.
Source: Oracle NetSuite Release Notes