Projects 2026.1: Bulk Task Inline Editing and On-Demand Revenue Recalculation

NetSuite 2026.1 ships two Projects enhancements aimed at reducing click-through on the Project record: an inline bulk task editor on the Schedule subtab, and on-demand revenue recalculation actions on the Project form. Both are UI-level features, but they have concrete implications for form customizations, scripts that touch job/projecttask records, and revenue arrangement workflows.

What changed

1. Add/Edit Tasks in Bulk (inline table)

• New Add/Edit Tasks in Bulk button on the Schedule subtab of the Project form (record type job) and on Project Templates.
• Opens an inline table where you can enter Name, Status, Planned Work (or Estimated Work, depending on your Project Management configuration), and Notes for multiple tasks at once.
• Default Status is Not Started. If Planned Work is empty or zero, the row is saved as a Milestone and flagged accordingly.
• Row order in the table determines display order in the Schedule view after save.
• On save, each row is materialized as a projecttask record (or milestone). Existing projects support the same flow for editing and adding tasks in bulk.
• The button is enabled by default on standard project forms and hidden by default on customized forms.

2. On-demand revenue recalculation on the Project record

• The Project record's Actions menu now exposes Recalculate Revenue Arrangements and Recalculate Revenue Plans, triggering recalculation for that single project on demand instead of waiting for scheduled jobs.
• Supports both calculation paths:
  • Project revenue recognition rules
  • Revenue recognition defined on sales transaction line items
• When an item's Revenue Recognition Rule (Revenue Recognition / Amortization subtab) is set to Default Percent Complete, revenue is recognized using the project's percent complete.
• If a project has its own revenue recognition rule, NetSuite ignores any rev rec settings on related transactions — the project rule wins.

Feature preconditions for revenue recalculation

• Project Management — enabled
• Advanced Revenue Management — enabled
• Charge-Based Billing — enabled
• Advanced Revenue Management in Configuration Mode — must be disabled

What an engineer/admin needs to verify

Oracle's notes are UI-focused and do not document any new SuiteScript API, REST endpoint, governance cost, or user event behavior. The following items are not stated in the source and should be confirmed in your sandbox before relying on them:

• Whether the bulk task save fires standard UserEventScript beforeSubmit/afterSubmit on each created projecttask, or batches them in a single transaction.
• Whether WorkflowAction scripts on Project Task trigger per-row.
• Whether the Recalculate Revenue Arrangements/Plans actions are exposed to SuiteScript (e.g., as a record.submitFields-style action or a workflow action) or are UI-only.
• Performance/governance impact when bulk-adding large numbers of tasks — test before letting PMs paste hundreds of rows.

What to do

1. Audit customized project forms. If your org uses customized Project entry/view forms (most do), the new button will be hidden. Go to Customize > Customize Form > Sublists and enable both View project - Show Add/Edit Tasks in Bulk button and Create project - Show Add/Edit Tasks in Bulk button on every form that should expose it. Repeat for project template forms.
2. Review Project Task user event and workflow scripts. Confirm they handle being invoked from the bulk inline save path. Pay particular attention to scripts that assume a single-record save context or that set defaults for status, estimatedwork/plannedwork, or milestone flags — the bulk editor will create rows with default Not Started status and auto-flag zero-work rows as milestones.
3. Validate milestone logic. Any downstream reports, saved searches, or scripts filtering on ismilestone should be tested against tasks created via the bulk editor with empty/zero Planned Work.
4. Confirm feature dependencies for revenue recalculation in target accounts: Project Management + Advanced Revenue Management + Charge-Based Billing all enabled, and ARM Configuration Mode disabled. If you run ARM in Configuration Mode anywhere, the new Actions will not be usable there.
5. Document the new manual recalculation path for your finance/PS team. It is a useful troubleshooting tool when revenue arrangements drift from project state, but it bypasses the scheduled recalculation cadence — set expectations about when to use it.
6. Check item rev rec rules. Anywhere you use Default Percent Complete on an item, recalculation will derive revenue from the project's percent complete; verify percent-complete calculation source (task progress vs. time entries) matches finance expectations before triggering on-demand recalculation in production.

Caveats

The source release note does not mention any changes to the SuiteScript N/record API surface for job or projecttask, nor any new REST record endpoints under /services/rest/record/v1/job. Treat this release as a UI/usability change with form-customization side effects, not a scripting API change, until Oracle's SuiteScript Records Browser for 2026.1 confirms otherwise.