Here two fun ones: • Attach a Client Script to the Address form(sub-record), put a console.log in

pageInit

, create a Sales Order and select a Customer, enjoy how your Client Script(attached to the address form) is triggered and the browser

console

complains about

console

not being defined. • From the same Client Script above do a

record.submitFields

to another record which has a UE deployed, enjoy how the submitFields triggers an EDIT event and also how

runtime.executionContext === runtime.ContextType.USEREVENT

. This is like saying an UE is being triggered by UE context (which should not be possible).

submitFields does trigger UEs though

@creece But shouldn't it be as an

XEDIT

(unless it's a record type/field that isn't available for inline editing)?

Yeah it should be XEDIT but the fact its triggering a UE isn't surprising.

I think I remember a thread about how if you record.submitFields on fields that are not inline editable, it actually triggers in EDIT mode instad of XEDIT

Honestly never heard of that but it sounds like thats how it works

it is functionally doing the record.load/set/save behind the scenes for you

@creece You are right no surprise

submitFields

triggering UE, but triggering

UE

with

EDIT

event and also with

runtime.ContextType.USEREVENT

when this is coming from a

Client Script

is weird.

Sounds like you gotta talk to NetSuite support for a bug maybe

your first point is probably the result of Client Scripts Attached to the Address Subrecord

@creece I don't need luck to handle that with support because is not happening hahaha 😂 I don't have the patience or the will to deal with NetSuite support anymore.