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

Ah, I think I follow. Is there a supported way to do that will work with context.form.clientScriptModulePath or do I need to resort to my backup plan of creating hidden fields with script code in them (or something of the sort)?

how are you creating your link element on the page?

are you using an inline html field? are you adding an inline html field using a user event?

I haven't actually added the link yet in the 2.0 script - I was trying to make sure the function was available via the console first - but in the 1.0 version that works I'm adding a text field in the UE. I'm planning on going that route in the 2.0 script once I get to that point.

you can use <@U29PVMVAR>'s suggestion of making the function global

```/**
 * @NApiVersion 2.x
 * @NScriptType ClientScript
 */
define([], function() {
  function pageInitTest(context) {
    console.log("Start page init");
  }
  window.testFunction = function(options) {
    console.log("Start test function");
  };
  return {
    pageInit: pageInitTest
  };
});```

Ah, cool, I didn't think to try to modify `window` within the define. I assume I could use any modules loaded in the define within that function without issue?

Shoot, it doesn't look like that'll work - when I try to update the script file, NetSuite's throwing the following error: `Fail to evaluate script: org.mozilla.javascript.EcmaError: ReferenceError: "window" is not defined.`

```/**
 * @NApiVersion 2.x
 * @NScriptType ClientScript
 */
require([], function() {
  function pageInitTest(context) {
    console.log("Start page init");
  }
  (function() {
    this.testFunction = function(options) {
      console.log("Start test function");
    };
  })();
  return {
    pageInit: pageInitTest
  };
});```

as an alternative, you can do what i suggest and select the element using javascript and set the onclick

```/**
 * @NApiVersion 2.x
 * @NScriptType ClientScript
 */

define([], function() {
  function pageInitTest(context) {
    console.log("Start page init");
  }
  if (document) {
    document.getElementById("whateverIdYouGiveToYourAnchor").onclick = function(
      options
    ) {
      console.log("Start test function");
    };
  }

  return {
    pageInit: pageInitTest
  };
});```

Oh interesting, I'll give both of those a shot. They both feel a bit DOM-hacky to me though, how much do you think either approach would be considered officially supported?

you added your own link anchor to the dom

only touch that and nothing netsuite will break

Makes sense. Thanks so much for your help!