Script Stacking Review

Active User Event and Client scripts deployed against Sales Orders, Invoices and Vendor Bills — attributed, ordered, and assessed for multi-provider stacking risk.

Section 01Threshold Test — Active User Event Scripts

Count of User Event deployments that are released, deployed, and whose parent script is not inactive. Client scripts are excluded from this test by definition but are reported separately below.

One Invoice and one Vendor Bill User Event (Approvals Workflow "Delete Exception") is restricted to the DELETE event only; on create/edit the effective counts are 6 and 5 — still over threshold.

Section 02Provider Attribution

Ownership was determined from three independent signals: the script.frombundle field, the File Cabinet path of the script source (bundle folders carry SuiteBundles/Bundle NNNNN; SDF SuiteApps carry SuiteApps/com.netsuite.*), and the script.owner employee. All three agree on every script.

Section 03Sales Order

7 active Client scripts from 6 products; 6 active User Event scripts from 5 products (2 further UE deployments are released but switched off).

User Event scripts — execution order

Client scripts — execution order

Red tags mark the three-way validateLine veto (ATB → USR → STE). Any handler returning false rejects the line; later handlers do not run.

Section 04Invoice

4 active Client scripts from 4 products; 7 active User Event scripts from 6 products — the highest User Event count of the three records.

User Event scripts — execution order

Client scripts — execution order

Section 05Vendor Bill

4 active Client scripts from 4 products; 6 active User Event scripts from 6 products.

User Event scripts — execution order

Client scripts — execution order

Vendor Bill is the only record with two saveRecord vetoes (SCM Landed Cost, SuiteTax Engine).

Section 06Stacking Matrix — Handlers per Event Phase

Number of distinct products with an active handler on each entry point. Cells at 3 or above are highlighted; 5 is the maximum observed. Approvals Workflow (NAW) fires on delete only and is marked †.

What happens when a user saves a Sales Order

Sequenced by the NetSuite record lifecycle, with the products holding a handler at each step. Highlighted steps are where a single handler can block or reshape the outcome for every product after it.

Section 07Risk Register

Only findings specific to this account. Severity reflects likelihood of user-visible or data-visible failure, not theoretical exposure.

Section 08Recommendations

1. Confirm execution order (30 minutes). Open Scripted Records for each of the three record types and compare the User Event and Client Script subtab order against Sections 03–05. If they differ, update this report; if they match, R8 closes.
2. Restrict execution context on the display-only User Events. customdeploy_15486_pay_info_*, customdeploy_lrcfm_ue_* and customdeploy_scm_is_transactions_ue_* implement beforeLoad to shape the UI. Limiting them to User Interface context removes them from CSV import, web services and scheduled runs at no functional cost. This directly reduces R7.
3. Delete or un-release the four latent deployments. Set status = TESTING (or remove) on the two EBP SS 1.0 deployments, the ATB UE and the PackShip UE so a future bundle update cannot silently re-arm them. Confirm with the bundle's update notes first — the 15486 script is the declared SS2 replacement for 2663.
4. Raise log level to AUDIT on the five beforeSubmit participants for one release cycle. The execution log is currently empty for all 20 scripts because 36 deployments run at ERROR. Two weeks at AUDIT will show real per-save governance consumption and any swallowed exceptions, then revert.
5. Reassign script ownership. Change owner on the two SCM-CPN scripts from employee 1252 to a live administrator so failure notifications land.
6. Adopt a per-record ceiling as policy. Before any new bundle or SuiteApp install, re-run the threshold query in Section 09 and require sign-off when a record type would exceed 3 active User Events or 3 validateLine/saveRecord vetoes. The query takes under a second.
7. Re-test the Sales Order line-entry path after each of STE, USR, ATB updates. These three share the validateLine veto; a regression in any one changes the user-visible behaviour of the other two.

Section 09Method, Assumptions and Source Queries

Scope and definitions

Assumptions

Queries

All queries are SuiteQL and ran read-only against the production account on 3 September 2026. They can be re-run as-is.

Q1 — Deployment inventory with entry points38 rows

SELECT d.id AS depid, d.scriptid AS dep, d.recordtype AS rt, d.status, d.isdeployed AS dpl,
       d.eventtype AS evt, d.loglevel AS lg, d.allroles AS ar, d.allemployees AS ae,
       s.id AS sid, s.scriptid AS sscr, s.name AS sname, s.scripttype AS st, s.apiversion AS api,
       s.frombundle AS bnd, s.owner AS own, s.isinactive AS inact, s.scriptfile AS f,
       CASE WHEN s.beforeloadfunction     IS NOT NULL THEN 'BL ' ELSE '' END
    || CASE WHEN s.beforesubmitfunction   IS NOT NULL THEN 'BS ' ELSE '' END
    || CASE WHEN s.aftersubmitfunction    IS NOT NULL THEN 'AS ' ELSE '' END
    || CASE WHEN s.pageinitfunction       IS NOT NULL THEN 'pageInit ' ELSE '' END
    || CASE WHEN s.saverecordfunction     IS NOT NULL THEN 'saveRecord ' ELSE '' END
    || CASE WHEN s.validatefieldfunction  IS NOT NULL THEN 'validateField ' ELSE '' END
    || CASE WHEN s.fieldchangedfunction   IS NOT NULL THEN 'fieldChanged ' ELSE '' END
    || CASE WHEN s.postsourcingfunction   IS NOT NULL THEN 'postSourcing ' ELSE '' END
    || CASE WHEN s.lineinitfunction       IS NOT NULL THEN 'lineInit ' ELSE '' END
    || CASE WHEN s.validatelinefunction   IS NOT NULL THEN 'validateLine ' ELSE '' END
    || CASE WHEN s.recalcfunction         IS NOT NULL THEN 'sublistChanged ' ELSE '' END
    || CASE WHEN s.validateinsertfunction IS NOT NULL THEN 'validateInsert ' ELSE '' END
    || CASE WHEN s.validatedeletefunction IS NOT NULL THEN 'validateDelete ' ELSE '' END AS entry
FROM scriptdeployment d
JOIN script s ON d.script = s.id
WHERE d.recordtype IN ('SALESORDER','INVOICE','VENDORBILL')
  AND s.scripttype IN ('USEREVENT','CLIENT')
ORDER BY d.recordtype, s.scripttype, d.id

Q2 — Default execution order (deployment creation sequence)38 rows · see A1

SELECT d.primarykey AS pk, d.scriptid AS dep, d.recordtype AS rt, s.scripttype AS st
FROM scriptdeployment d
JOIN script s ON d.script = s.id
WHERE d.recordtype IN ('SALESORDER','INVOICE','VENDORBILL')
  AND s.scripttype IN ('USEREVENT','CLIENT')
ORDER BY d.recordtype, s.scripttype, d.primarykey

Q3 — Threshold test (re-usable policy check)returns record types over the limit

SELECT d.recordtype, COUNT(*) AS active_ue
FROM scriptdeployment d
JOIN script s ON d.script = s.id
WHERE s.scripttype = 'USEREVENT'
  AND d.status = 'RELEASED' AND d.isdeployed = 'T' AND s.isinactive = 'F'
GROUP BY d.recordtype
HAVING COUNT(*) > 3
ORDER BY active_ue DESC

Q4 — Script source location and folder lineage (provider attribution)19 files

SELECT f.id, f.name, f.folder, mf.name AS foldername, pf.name AS parentname,
       f.lastmodifieddate, f.filesize
FROM file f
LEFT JOIN mediaitemfolder mf ON f.folder = mf.id
LEFT JOIN mediaitemfolder pf ON mf.parent = pf.id
WHERE f.id IN (24710,5015,7620,90318,24736,15327,5093,7568,24576,5021,23955,1148,
               5048,15869,24196,15870,5899,5092,5062);

-- folder ancestry to the SuiteBundles / SuiteApps root
SELECT f1.id, f1.name AS l1, f2.name AS l2, f3.name AS l3, f4.name AS l4, f5.name AS l5
FROM mediaitemfolder f1
LEFT JOIN mediaitemfolder f2 ON f1.parent = f2.id
LEFT JOIN mediaitemfolder f3 ON f2.parent = f3.id
LEFT JOIN mediaitemfolder f4 ON f3.parent = f4.id
LEFT JOIN mediaitemfolder f5 ON f4.parent = f5.id
WHERE f1.id IN (3129,3141,3037,2800,1667,2135,3018,401,384,2347,934,962)

Q5 — Script owner resolution

SELECT id, entityid, firstname, lastname, email, isinactive, title
FROM employee WHERE id = 1252

Q6 — Execution-context coverage per deploymentall 38 rows: 37 contexts, no restriction

SELECT d.scriptid AS dep,
       LENGTH(d.executioncontext) - LENGTH(REPLACE(d.executioncontext, ',', '')) + 1 AS ctxcount
FROM scriptdeployment d
JOIN script s ON d.script = s.id
WHERE d.recordtype IN ('SALESORDER','INVOICE','VENDORBILL')
  AND s.scripttype IN ('USEREVENT','CLIENT')

Q7 — Workflows on the same records (supplementary, A5)

SELECT internalid, scriptid, name, recordtype, recordtypes, isinactive, releasestatus,
       frombundle, initoncreate, initonvieworupdate
FROM workflow WHERE isinactive = 'F' ORDER BY recordtype

Q8 — Execution-log presence0 rows · see A4

SELECT n.scripttype AS script, n.type, COUNT(*) AS cnt
FROM scriptnote n
WHERE n.scripttype IN (2386,477,1201,3365,2389,1274,436,1155,2192,418,2051,135,
                       473,1793,2182,2098,801,1794,476,423)
GROUP BY n.scripttype, n.type ORDER BY cnt DESC

Source tables

scriptdeployment · script · file · mediaitemfolder · employee · workflow · scriptnote. Column names were verified against a single-row SELECT * on each table before use. Note that scriptnote.scripttype holds the script internal id, and workflow exposes internalid rather than id.