Hiding elements - HUD control

Alan Cooke Thanks, anything helps to make the CRM in its vanilla form as user-friendly as possible. 

Alan Cooke Hi again, Alan. Was wondering if you have anything more to add to this. 

I'm especially curious to hear if you have any advice on blocking the + button on the table overview (spreadsheet-style tabular views)?

Ruben Hi, I think this is what you are looking for...

.i-light-grey.i-plus{display:none}

Ruben Right, sorry about that. I realized after I posted that the Formula field version won't work if just the Table view is open. This is code you can put in Trigger after open and if you want you can put all of the rules there.

dialog("Console CSS Modifier", html("<script>
    var styleSheet = document.styleSheets[2];
    styleSheet.insertRule('.i-light-grey.i-plus{display:none}');
    var interval = setInterval(() => {
        var bt = document.querySelector('.nx-alert .nx-button-text');
        if (bt) {
            bt.click();
            clearInterval(interval);
        }
    });
</script>"), ["close"])

You need to add styleSheet.insertRule for each additional rule.

Sean Thanks. Yes, this actually helps remove the + symbol, but only visibly. The problem is that when people search for an entry, then "misclick" just underneath it, they create a new file

And there's no script-based function of blocking new records, only through restriction of rights. It is also not possible to block creating new entries entirely, and then "allowing" it through a button or similar, it seems if people are restricted from creating with the "+" they are equally restricted when they are pushing a button.

I haven't tried do as server though, I wonder if that would make a difference. Anyway, I will mention it at the Open Consultation Hour in 10 minutes

Sean Update: According to Ben Lucas, there is no known possibility to actually block this function at the moment but is planned for one of the next bigger updates. 
 

The only other way I know to work around this is to automatically trigger "delete the last record"  on the "when creating new record" trigger, at least that can be controlled via boolean field or other script etc.

And then I can at least avoid accidental empties. Not a good choice for billing, of course. And the disadvantage is that you end up having a bunch of deleted hidden records.