i think i'm getting close 😅 a bit puzzled by this one though:

const rec = record.create({
  type: record.Type.SALES_ORDER,
  isDynamic: false
});
...
const customerId = 268554; // actually the value returned by a search
rec.setValue('entity', customerId);

gives an error:

..."name":"INVALID_KEY_OR_REF","message":"Invalid entity reference key 268554."...

i can see in the UI that a customer exists with this id is this some kind of incorrect permissions? (i don't think so - i basically copied celigo's permissions for starters) is

entity

the wrong field? do i have to use dynamic mode for some reason?

Is the customer inactive?

i don't think so - customer was created via the api, so it's whatever the default is. inspecting the customer record with "netsuite field explorer" extension, i see

isinactive: "F"

only other thing I can thin k of is that the role you're using doesn't have access to the subsidiary of the customer

is there a way to get an actual failure reason? (e.g. have it tell me access was denied, if it's a permission problem)

Apart from entering an enhancement request that will likely never get done, no

makes me feel better about spending whole days on creating useful error messages lol.

It does return a number, but NS has a few inconsistencies when it comes to internal ids. You'll expect a number, and you may get a number, a string, or a float

a float? 😱

it happens 😕

what does that even mean

var recId = myRec.save() might return 123481.0

oh

@hitc/netsuite-types is the most accurate typings available for NetSuite. The inconsistency of NS to use numbers and strings for ids makes me still use

==

over

===

in many cases

that makes some amount of sense