FSM Mobile 2026.07.1 Changes for Early Access

FSM SuiteApp 2026.07.1, available only for early access testing in sandbox accounts, updates FSM Mobile status visibility, loading and sync-error feedback, configuration properties, navigation, expressions, localization, and selected usability behavior. Administrators should validate configuration changes in sandbox, particularly permissions, automatic mapping, and Track Service Time.

What changes in FSM Mobile status visibility?

FSM Mobile adds status indicators at the app, task, mobile-tab, and record levels. The indicators identify active sync, draft, error, and offline statuses.

When the app is offline, a warning banner remains at the bottom of every page as technicians move through the app. During synchronization, the active-sync icon appears consistently wherever Active Sync status is shown.

The app-level counter appears at the top of the task list and counts records with active sync, draft, error, or offline status. When the app is offline, its icon shows Offline and the counter includes records pending synchronization.

The task-level counter appears at the top of each task and includes only records with draft or error status. When multiple statuses apply at the app, task, or mobile-tab level, FSM Mobile displays the highest-priority status:

1. Offline
2. Active Sync
3. Draft
4. Error

These changes complement the broader status badge updates on Agenda task cards, which address task-state visibility elsewhere in FSM Mobile.

How are loading and sync failures shown?

Loading indicators appear on the task list and mobile tabs while the app retrieves task data, user resources, or mobile-tab data from the server. If loading fails, an error banner appears in the affected area.

If task data or user resources fail to load, the task list appears empty and technicians cannot select Add Tasks. This distinguishes a data-loading failure from an ordinary empty assignment list.

After a failed sync attempt, a dedicated error icon appears on the affected record. Technicians can retry sync without changing record data. The icon remains until the record data changes or a retry succeeds. If a technician restores values that caused the original failure, the icon may reappear.

Teams testing mobile reliability may also want to include the related barcode scanning reliability changes in the same device and connectivity test plan.

What does the navigation bar display?

The navigation bar can show up to two lines of information for the current mobile tab and its record or draft:

• The first line displays the configured mobile-tab name. If that name is blank, the line remains blank.
• For an existing record, the second line displays the label and value of the first mobile-tab element that provides title information.
• For a draft with configured title information, the second line displays Unsaved Draft.
• If no element provides title information, only the first line appears.

Administrators should review title-information configuration and tab names when testing forms with similar layouts or records.

How can task completion and record actions be controlled?

A new cancomplete property in the mobile event map controls whether tasks can be completed in FSM Mobile. When cancomplete returns false, the Complete button is dimmed and the app does not start a completion request.

Default completion behavior remains different by event type:

• Only the task assignee can complete Customer Relationship Management (CRM) tasks by default.
• Any mobile user can complete project tasks by default.
• Other mobile event types retain their existing completion behavior unless an administrator configures cancomplete.

The new create, edit, and delete properties independently control technicians' record permissions in FSM Mobile. Existing readonly, min, and max rules continue to apply. However, this release removes the readonly rule from the resource level of the FSM Configuration. Administrators should migrate applicable resource-level readonly rules to edit.

Unconfigured permission properties, and expressions that do not evaluate to true or false, default to true. Permission testing should therefore include each property independently and confirm that expressions return Boolean results.

For additional configuration changes delivered in the same release cycle, see the FSM Mobile app configuration enhancements.

How does automatic NetSuite field mapping work?

Administrators can set a mobile tab's automap property to true to map elements without defining every corresponding field in article.map. By default, automap is not set to true for any FSM Mobile tab.

At runtime, FSM reviews unmapped elements and checks whether each element ID exactly matches a field ID on the record specified by article.record. A matching element is treated as mapped at runtime. Existing explicit mappings continue to apply and take precedence. The property does not modify the FSM Configuration.

{
  "automap": true
}

Before setting automap to true, administrators must confirm that each intended element corresponds to an existing NetSuite field and that the IDs match exactly. An ID mismatch can cause the mobile-tab request to fail and prevent tasks from loading in FSM Mobile. Introduce the setting in sandbox and validate the tab before broader use.

How can heading blocks organize mobile forms?

Static heading blocks organize long mobile forms without placeholder fields or inline HTML workarounds. Configure a mobile-tab element with the heading block type and a label.

The level property accepts 1, 2, or 3, in decreasing order of visual prominence. An invalid value defaults to 1. A heading spans the full content width and follows existing element-ordering logic: index controls placement when defined; otherwise, FSM Mobile uses element order.

Heading blocks affect layout but are excluded from the save payload. Oracle identifies SuiteAnswers ID 1046936 as the supporting configuration reference.

Which date and time expression helpers are available?

Mobile expressions now include format(date) and now() helpers for date, time, and datetime values. They work in mobile expressions, including dynamic resource-block properties such as min, max, and value.

Values for value, min, and max must resolve to the format required by the target element. FSM ignores a configured property whose result does not match that format.

The required stored value is independent of the localized format displayed to the user.

FSM automatically migrates existing nxc_now() expressions to corresponding helper replacements while preserving existing checkbox conditions. It stores migrated expressions in a copied configuration record named Auto Configure xxxx: Migrate nxc_now expressions.

What other configuration changes require review?

After a mobile form closes, FSM Mobile evaluates required expressions to determine whether a mobile tab is complete. If an expression returns false, dependent mobile tabs or the Complete button remain available even if an empty element exists. Previously, required expressions were treated as true outside an open form, and an empty element could cause the mobile tab to be treated as incomplete.

Track Service Time is managed through the Boolean time.timetracking FSM configuration option. Accounts that had the feature enabled before the update retain that setting. Before enabling Track Service Time in production for the first time, administrators must test it in a sandbox account.

How is FSM Mobile license use monitored?

Employee records no longer display current and total mobile-license counts beside the Field Service Mobile User field. Administrators must create a saved search and compare its results with the Field Service Management Users row on the Billing Information page.

Open the Billing Information page through Setup > Company > View Billing Information. Oracle identifies SuiteAnswers ID 1046924 as the reference for creating the saved search.

Which locale and usability updates are included?

FSM Mobile supports Portuguese (Portugal) through the pt_PT locale, displayed as Português (Portugal). Translations are available only for accounts in Portugal with Portuguese (Portugal) set as the default language.

The release also changes select fields, search behavior, and Service Report images:

• A searchable select field in a new table row opens with an empty search field and unfiltered options rather than retaining text and filtering from the previous row.
• A select field with a saved value shows the matching current option label when the form reopens. If no matching option exists, it shows the saved-value label.
• When technicians return to a mobile tab with a saved search keyword, the search field opens with that keyword and the list remains filtered. This also applies filtering on mobile tabs without remote search when the field reopens.
• After the app is refreshed or reopened, the task-list search field displays saved search text and the task list remains filtered by that text.
• Images linked to completed tasks and project tasks display on Service Reports regardless of the customer's Field Service Language. Previously, images could be omitted when the selected language was not English or French.

Who This Affects

• FSM administrators: Review resource-level readonly rules, permission expressions, cancomplete, automap, time tracking, and license-monitoring procedures.
• Mobile technicians: Receive status, loading, navigation, sync-error, search, and select-field behavior updates.
• Configuration developers: Can use format(date), now(), automatic mapping, heading blocks, and independent action-permission properties.
• Support teams: Need to recognize empty task lists caused by task-data or user-resource loading failures and the record-level retry indicator.
• Billing administrators: Must use a saved search and the Billing Information page to monitor mobile-user license usage.

Key Takeaways

• FSM SuiteApp 2026.07.1 is currently available only for early access testing in sandbox accounts.
• FSM Mobile adds app-, task-, mobile-tab-, and record-level status feedback, loading indicators, and retry support for failed record sync.
• cancomplete, create, edit, and delete add configurable control over task completion and record actions; resource-level readonly rules require migration to edit where applicable.
• automap can reduce article.map entries, but exact element and NetSuite field ID matches are required to avoid mobile-tab request failures.
• The release also includes heading blocks, date and time helpers, Track Service Time configuration, Portuguese (Portugal), license-monitoring changes, and targeted mobile UX fixes.