I am trying to only display a button on a sales order, when I'm viewing it. When editing, or anything else, I want that to be hidden but for some reason when I hit the "edit" button on the SO I can still see it appearing, even though in the logs isHidden and isDisabled is true in both cases - is there something I am doing wrong down below, that the button isn't hiding when I hit "edit" on the SO?

/**
 * @NApiVersion 2.x
 * @NScriptType UserEventScript
 * @appliedtorecord salesorder
 */
define([], function() {
  function beforeLoad(context) {
    log.debug({
      title: 'Context Type',
      details: context.type
    });

    var button = context.form.addButton({
      id: 'someButtonID',
      label: 'A Button',
      functionName: 'onButtonClick'
    });
    context.form.clientScriptModulePath = 'SuiteScripts/someJsFile.js';
    button.isHidden = context.type != context.UserEventType.VIEW;
    button.isDisabled = context.type != context.UserEventType.VIEW;

    log.debug({
      title: 'Button',
      details: button
    });
  }

  return {
    beforeLoad: beforeLoad
  };
});

Try not adding the button in the first place if

context.type != context.UserEventType.VIEW

if(context.type != context.UserEventType.VIEW) return;

@ehcanadian I have tried this before with no luck as well, but will give it another try. Could it possibly be because var is not block scoping properly?

Your button id must start with

custpage

and be all lover case as well. Is what you posted the full script?

@ehcanadian the code above is the full user event script, I've just gone and changed the names around for this post, but the actual button id starts with "custpage_" as well and is all lower case 🙂

How are you updating the file? If it's using sdf maybe you're getting a cache issue. Script looks fine

I had a feeling if maybe it was the cache, I'll try to clear it and see if that helps any, or maybe even ask my colleagues to try it on their end. I'm just uploading it through the actual script file in NS, apologies, not sure what SDF is 🙂

FYI avoiding adding the button is better than adding it then hiding / removing it if context is the only consideration.