Hide Update and Delete Buttons

[Vineetha Rohra1]

I have a custom table. When i open its form, fill it and save it a record gets generated.

When i open this particular record, update and delete buttons appear on the form which i dont want to appear.

How to hide them on load of the form of any record. I mean if i open that record, these 2 buttons should not be visible on the form.

Any help please.

[Vineetha Rohra1 · Accepted solution]

Hi Brian,

Thanks for the suggestion, i tried modifying condition for update ui action and added condition as tablename != (my custom table's name) and it worked. I did the same for delete ui action as well.

[sigvalnatanaelb]

that solution wont work for example with a scoped applications, unless you wish to have a separate update set for this, but I dont recommend changing the out of the box features like that, keep in mind that doing so will add this ui action to the skipped log that you'll have to go through when upgrading your instance to the next version of service now, meaning any future updates for this will be marked as skipped because you have made come manual custom changes to this out of the box record, so that all updates on this will have to be solved by merging manually. This is what is nice about scoped applications, because it will remind us whenever we are trying to modify something out of the box. 

the correct way of hiding these buttons is to make a custom update button for your table, overriding the default one, and then mark this one as inactive. 

you an easily do this by locating the default UI action for update (check ui action having name like update and table sat to global), then just change the table from global to your own table and set active to false and then hit insert and stay. the trick to override default out of the box global ui actions is to just make sure that you make a new ui action for your own table having the same action name (not just the name) the action name for global update ui action is: sysverb_update

[sigvalnatanaelb]

sorry, marking it as inactive will just result in the default one re appearing, instead you have to keep your custom one active, but instead just add false in the condition