Disable insert button?

[Jane]

I think I'm probably missing something obvious.

I want to conditionally disable the Insert button.  The template appears to support doing that, but it removes the button altogether rather than disabling it (pic).

Setting the "Disabled IF" condition on a regular button placed as a field on a form tab works as expected.

I can OMIT() template code and write my own routine to make it work on a browse, but am I misinterpreting the template option's intent?

edited to add:  nt 12.38
 
Jane

[Bruce]

It's a bug. That disable was being applied to the small inline button, not the button underneath.
I'll fix that for the 12.39 build.

Incidentally note that the "disable" is only a visual thing. The user could still use the developer console to enable the button, and then add a record...

[Jane]

LOL...  I never use the row insert buttons so that never occurred to me...

Thanks, Bruce.

This is not a high-security item.  Rather, I don't want someone creating an audit record for a date that has not yet come.  Instead of removing the button I decided to leave it tantalizingly in view but disabled, with a message saying that the future will come in its own time.

Just because I'm a jerk, and I can...   

A fix would be nice but I just added my own logic to set the flag in the call to CreateStdBrowseButton.

BTW... this may be intentional but it seems that the [Start of "Set jQuery Update Buttonset Options" Priority 5000] embed in the GenerateUpdateButtonsAbove and GenerateUpdateButtonsBelow routines share code.  Put something in one, close and open the procedure, and the code appears in the other one as well.

Cheers,

Jane

[Bruce]

that is indeed intentional.

[Jane]

that is indeed intentional.

Makes sense that it would be since both routines are doing almost the same thing.  It just surprised me because I was using that embed for part of the OMIT to substitute my own code and noticed that the end of the omit wound up in both places.

[Jane]

Thanks for the 12.39 fix.