2025.10.5 Mobile App Fixes: Multi-Record Sales Orders, Geolocation on Uploads, Default-Value Form Save

NetSuite patch 2025.10.5 addresses three issue fixes, all related to the NetSuite mobile app and form rendering. There are no new features or API changes — these are purely bug fixes. No SuiteScript, REST, or SOAP contract changes are called out.

What changed

1. Multiple Sales Orders now created correctly when max > 1

When the Sales Order tab on a mobile form is configured with a max property greater than one, submitting the new Sales Order form multiple times previously overwrote earlier entries instead of creating separate records. Each submission now correctly creates a distinct salesorder record.

Impact: If you have custom mobile configurations or SuiteScript beforeSubmit / afterSubmit User Event scripts on Sales Orders that deduplicate or count records, verify that the fix has not altered your expected record counts. Any workaround logic you added to compensate for the overwrite bug should be reviewed and likely removed.

2. Geolocation now included in file descriptions on upload

Uploading files via the File block, Image block, or Files tab in the mobile app now writes both a timestamp and geolocation coordinates into the description field of the resulting File Cabinet record (file.description).

Impact: If you have scripts or saved searches that parse or rely on the description field of File Cabinet records (record type file), be aware that the format now includes GPS coordinates. Any string-matching logic against that field may need updating. The release notes do not specify the exact coordinate format (e.g., decimal degrees, DMS) — verify in your environment after the patch applies.

3. Save button now shown for forms with all default values

Mobile forms where every required field has a default value previously hid the Save button, preventing submission without manually changing a value. The button now renders correctly.

Impact: Minimal for most environments. If you intentionally relied on the missing Save button as a gate (e.g., forcing users to review defaults before saving), that behavior is gone.

What to do

1. Review Sales Order workarounds. If you deployed client-side or server-side scripts to work around the duplicate/overwrite bug on mobile multi-submit Sales Orders, test whether those workarounds now create unintended duplicates and remove them if so.
2. Audit File Cabinet description parsers. Search your codebase and saved searches for references to the description field on file records. Update any regex or string-matching logic to account for the new geolocation data appended on mobile uploads.
3. Test default-value forms. If you have mobile forms where all required fields carry defaults, confirm the Save button appears and that submission works end-to-end in your sandbox after the patch rolls out.
4. No API migration required. These are behavioral fixes with no changes to SuiteScript modules, REST endpoints, or SOAP WSDLs.