This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

I have a ghost in the ~shell~ system

*Context*: I have a Custom Transaction named `spc`. The custom transaction `spc` is of type Purchase, so I can have some default fields as vendor, date, period, account, currency, memo, item list. You get the idea.

*Problem*: One of this native fields `memo` is being populated with a string every time the selected `vendor` changes. Hard to tell if `vendor` is the trigger, because changing `vendor` sources the account, subsidiary, etc. The string in `memo` varies between `"TBD"` and the name of the Account that gets sourced natively when the vendor changes.

Now, you may guess: A Workflow or a script is setting the value, right? Well, there is no workflow or script. Confirmed using the *Scripted Record page*, and the *NetSuite Scripted Records* Chrome Extension. After this, I did wonder if `memo` was really a native field, maybe it was a custom field with sourcing enabled. But no, its a native field.

*So, is there any other way to know which script, if any, is triggered in this case?* Maybe using the dev tools in Chrome or something similar? If the network tool fails me too, maybe block the field so I can check logs for errors in other script attempting to change it?

image.png

Oks, using Firefox Dev Tools, I used the Debugger &gt; Search

And found the suspect, but it just says the file is `source1179`, now... How can I get to this generic named file?

I guess it's a minified version :thinking_face:

Remember that you can attach client scripts to specific forms via the form itself (customize form) without script deployment and you would not see those using extensions (not sure about Scripted Records).

I guess in `Custom Transaction Form &gt; Custom Code &gt; SCRIPT FILE`

But is empty :sadblob:

No ideal, but you can always create a custom memo field: My Awesome Normal Memo Field.
And hide the crazy memo field in the form.