Question: When you need to 'edit' a record, are y...
# suitescript
d
Question: When you need to 'edit' a record, are you more apt to load it in
dynamic
mode or
standard
mode?
s
I almost never find a reason to use dynamic mode.
💯 1
c
Same - dynamic just seems to cause unnecessary headaches
d
Wow, really? What about sourcing and ensure the value you set on the record are actually correct? Especially in a OneWorld instance where you have subsidiaries/segments/etc that all need to aligh properly?
b
i mostly only use dynamic mode if i want select options
most of the time you dont write logic thats conditional on sourcing
if you dont do logic depending on what values netsuite sources, dynamic mode just makes you pay more attention to the order you set fields in
s
for the the exception is any time you do depend upon sourcing. IIRC things like applying a payment to an invoice.
b
in the worst cases, i would not rely on the apply sublist to source correctly
its affected by user filters and sublist row limits
i prefer using default values to limit the rows to what i want them to be
r
My theory is only use dynamic when the standard fails
d
Woah. I would have guessed heavily toward
dynamic
mode. No one ever runs into an issue where something they do in the UI doesn't behave that way in does in script?
r
in dymanic mode it requires field be set in order while in Standard is does not. thus less hair pulling when you get a error