What exactly is this doing?
# suitescriptc
Craig
05/01/2020, 1:44 AMWhat exactly is this doing?
b
battk
05/01/2020, 1:46 AMc
Craig
05/01/2020, 1:49 AMSo the user entered a script param into a record and this is reading that?
Craig
05/01/2020, 1:51 AMMaybe not - reading script param docs now
Craig
05/01/2020, 1:51 AMSo it's a param that the user can create on the deployment record.
b
battk
05/01/2020, 1:52 AMIts usually a field on the script deploymeny
c
Craig
05/01/2020, 1:52 AMWhat's the purpose?
b
battk
05/01/2020, 1:53 AMIf you want a field specific to a script, thats what you use
c
Craig
05/01/2020, 1:53 AMAllowing you to modify script execution without editting code.. I usually see that done via custom fields on recods but i guess this has *'some'*use
b
battk
05/01/2020, 1:54 AMUncommonly you can also make it company level
battk
05/01/2020, 1:54 AMI havent seen the user level one yet
c
Craig
05/01/2020, 1:54 AMOne year of SS2 and this is the first time I've seen this used
Craig
05/01/2020, 1:57 AMI'm finding that code from NS PS seems to be pretty messy / written quickly
Craig
05/01/2020, 2:00 AMwhat a great day - learnt something completely new. I see the value in script params now but it's adding complexity.
Craig
05/01/2020, 2:00 AMThanks for the link!
Craig
05/01/2020, 2:01 AMSeems that the error is coming from some crap code in an NS PS module that is linked too from the UserEventScript
Craig
05/01/2020, 2:01 AMI'm not going to modify the module code, I'll come up with something in the usereventscript to mitigate calling the module function with bad data. I assume that's the best way to go as NS PS may come back one day and not expect their modules to have been edited.
a
Alex Hirota
05/01/2020, 2:11 AM@Craig Just as an additional note I’ve had great results using the current script parameters in Mass Updates. Having a selectable script parameter allowed me to just make one script that updated the specific fields, and gave my users controls to set those fields to what they wanted.
c
Craig
05/01/2020, 2:12 AMYeah I can see the benefit - there's a lot of code here that does that based on a value in a custom record but I can see the value of doing that with a script param.
e
ehcanadian
05/01/2020, 2:13 AMI use them to determine what search will be used for getInputData in M/R's so that different criteria can be selected without having to modify any code.
c
Craig
05/01/2020, 2:13 AMI feel like I just found a hammer and now everything is a nail - I'm going to find ways to use this 🙂
😂 1