2026.1 Patch: Map/Reduce & Scheduled Script User Context Clarified, Cash Refund CSV Import, OAuth 2.0 DCR Field

What changed

SuiteScript: User and role context for Map/Reduce & Scheduled Scripts

Oracle updated documentation to explicitly state which user and role a script runs as when triggered via each submission method. This applies to:

• Scheduling a Map/Reduce script submission
• Submitting an on-demand Map/Reduce deployment from the UI
• Submitting an on-demand Map/Reduce deployment from another script
• Scheduling a one-time or recurring Scheduled Script submission
• Submitting an on-demand Scheduled Script instance from the UI
• Submitting an on-demand Scheduled Script instance from another script

This is a documentation-only change, not a runtime behavior change — but it matters. If your Map/Reduce or Scheduled scripts rely on runtime.getCurrentUser() or role-based permission checks, you should verify that the documented execution context matches your assumptions. Scripts submitted from other scripts may inherit the calling script's user/role rather than the deployment's configured values, depending on the method used.

CSV Import: Cash Refund records now supported

The CSV Import Assistant now supports Cash Refund records. Previously, importing cash refunds required SuiteScript or web services. You can now bulk-import these via Setup > Import/Export > Import CSV Records.

OAuth 2.0: New "Client Name for Dynamic Client Registration" field

A new field, Client Name for Dynamic Client Registration, has been added to Integration records (Setup > Integration > Manage Integrations). This field is relevant if you use OAuth 2.0 with Dynamic Client Registration (DCR). The source does not specify the internal field ID — inspect the record in your sandbox or check the Records Browser for the integration record type.

SuiteApprovals: 1,000-record display limit documented

The Review Documents Awaiting Approval landing page and both SuiteApprovals portlets (Records for Approval and SuiteApprovals Reminders) have a hard display limit of 1,000 records. If your approval queue exceeds this, records beyond the limit will not appear in the UI. This was previously undocumented.

Account Setup: Elimination journal entry tracking

A new feature, Track Deletion and Creation of Elimination Journal Entries During Intercompany Elimination Process, has been added. The source provides no further detail on the mechanism — check the Intercompany Elimination preferences in your account and the system notes on elimination journal entries for new tracking fields or audit trail entries.

Order Management: NetSuite Pay enhancements (SuiteApp 2026.1.0)

The NetSuite Pay SuiteApp has been updated to version 2026.1.0 with enhancements to the merchant account application workflow. This is a managed SuiteApp — updates are delivered automatically. Review the SuiteApp release notes for specifics on any API or record changes.

What to do

1. Audit Map/Reduce and Scheduled Script execution context. Review scripts that call runtime.getCurrentUser(), check roles, or rely on permission-sensitive operations. Cross-reference with the updated help topics to confirm your scripts execute under the expected user and role — especially scripts submitted programmatically from other scripts.
2. Leverage Cash Refund CSV Import. If you have custom scripts solely for bulk-importing Cash Refund records, consider retiring them in favor of the native CSV Import path.
3. Check OAuth 2.0 integrations using DCR. If you use Dynamic Client Registration, inspect the new Client Name for Dynamic Client Registration field on your Integration records. Determine whether you need to populate it for existing integrations.
4. Plan for the SuiteApprovals 1,000-record cap. If your approval queues regularly exceed 1,000 pending records, build saved searches or workflows to surface items the portlets will not display.
5. Review intercompany elimination audit trail. After the update, run a test elimination and check system notes or new sublists on elimination journal entries for tracking data.