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

<@U29PVMVAR> I think I figured it out. I just need to verify.

Here's what I had to do for some buttons I had in an INLINE HTML field

```
define([...], function (...) {

// other stuff

    function toButton(applicant) {
        /* XXX When this client script is attached via `form.clientScriptModulePath`, the click handler function
         * is not exported correctly into the browser global context, so supportApplicant() is undefined. This
         * workaround requires the module at runtime as well in order to property invoke supportApplicant()
         */
        var onclick = "require([\"" + CLIENT_PATH + "\"], function(mod){mod.supportApplicant(" + applicant.id + ");})";
        return [
            "&lt;button type='button' id='btn_", applicant.id,
            "' onclick='", onclick, "&gt;",
            "&lt;/button&gt;"
        ].join("");
    }

    function supportApplicant(id) {
      // awesome click handles
    }
 
    exports.supportApplicant = supportApplicant;
    return exports;
});
```

`toButton` just ouputs the HTML of the button that I then pass to `setSublistValue()` for the Inline HTML field

had to do that `require()` mess within the `onclick` attribute

Thanks Eric. Part of my issue is the file path in the SDN is different from that of the path when bundled.

I think with `require()` you should still be able to use the `/.bundle123/` or whatever that syntax is for SuiteApps, but I've never done it myself

I've used the /.bundle123/ before. It works.