today's rant: why can't NetSuite be the slightest bit consistent. I swear, every time I use

url.resolveRecord()

I forget that it's

recordType

and not just

type

.

Definitely agree on this being annoying. Along these lines, `N/ui/serverWidget`'s

Form.getField()

takes an

id

option, but `N/currentRecord`'s

CurrentRecord.getField()

takes

fieldId

. That one's even more confusing to me because it's the same base functionality, just in a different context.

ugh

Convert to using Typescript, you'll never be wrong again.

Yeah, but as Eric mentioned earlier, that's not really the point - seeing this inconsistency within NetSuite's code just shows how disjointed everything is in their development process. They had such a great opportunity when building SS2.0 from scratch (or at least approximately from scratch) to get everything consistent and they clearly dropped the ball there. Not only with varying option names across different modules like we're discussing here, but in a number of other places too, e.g. the places that still use

'T'

and

'F'

for checkbox fields.