That's the correct approach, so we'll need more co...
# suitescript
e
That's the correct approach, so we'll need more context/info
m
@erictgrubaugh: This doesnโ€™t set the customer as individual, always creating as customer = company. FYI am using dynamic = true on customer record create
e
What script type? What entry point? Please share code.
m
its a mapreduce script and getting this error
Field must contain a value.
message has been deleted
@erictgrubaugh: Am not sure why Netsuite is not accepting the isperson = โ€˜Tโ€™
e
That's how I'm doing it in a Map/Reduce currently running in a Production account.
but I don't use Dynamic mode
I assume there is more code after that, and that you are at some point
save()
ing the record
m
Yes, Let me try without dynamic mode
s
wait a second, if
isperson
is a checkbox, that's a boolean in SS2.x (with the exception of client scripts perhaps, I haven't done one of those in a while)
I thought one of the big wins of SS2 field access was representation of checkboxes as
boolean
?
e
Yeah
isperson
a radio button though
and those have never had any love in SuiteScript
and that's still true in 2.x
s
ah, my faith was about to be shaken there. sorry to interrupt - forgot that isperson is not a checkbox ๐Ÿ™‚
m
@erictgrubaugh: Figured out that dynamic mode = false worked out. Thank You๐Ÿ‘
๐Ÿ‘ 1
s
dynamicmode = false is the default - as a general rule I stick to that unless I actually need dynamic mode.
e
I don't recall a time in 8 years of NS dev where I needed to use Dynamic mode. Note I'm not saying "never use it", just that you should only need it in highly specific situations