https://netsuiteprofessionals.com logo
Join Slack
Powered by
considering I only have about 5 fields on one reco...
# suitescript
k
considering I only have about 5 fields on one record I want it to look at.
s
You can write the XEDIT record value to a log and look at it.. that should help with making decisions.. If I ever need to modify a record upon Inline Edit, I always Load that record when it comes in on the UE so I have access to the full record, and then I can save it properly.
k
That's not a bad idea, thanks.
Granted, this is on an aftersubmit (i know.. I know...)
Though I wonder if I could make it a before submit because it's not that complex...
b
making your script work with xedits is not that difficult
you are supposed to get a list of fields that changed, and only do your logic on those
s
@KevinJ of Kansas BeforeSubmit would work as long as you don't need a reference to the existing transaction on CREATE.
k
Fudge. Ok, After submit it is.
And I'm way out in left field on this one, this isn't a standard "oh do this when this" it's "create a custom record that creates another custom record and schedule a map reduce to do stuff" - I've basically built an application within NetSuite, using NetSuite, that barely touches NetSuite records.
Or rather NetSuite standard records.
All because these people have to have customer specific pricing - using formulas, quantity breaks, and freight charges, and all kinds of other whacky logic.
b
although i would say that afterSubmit is probably the correct place to do this, i give the opposite advice of shayes and say dont load the record and just follow the documentation's method for handling xedits
2 Views
Open in Slack
PreviousNext
Powered by