How to remove the Plus-Sign ("Create a new record") button from Global Command Bar in a model-driven app?

[Dave-Storey]

I have a model-driven app with many custom tables, some of which have Quick Create forms, and therefore have the "Leverage quick-create form if available" option turned on.  For many of these tables, I need for the new record to be created in the context of its parent record.  I enforce this in my app by using Ribbon Workbench to hide the "New" button on the "HomepageGrid" and "Form" areas, and leave it visible on the "SubGrid" area only.

The problem I have is that the Global Command Bar that appears at the top area of the application contains a plus sign button (+) which shows all tables which have the "Leverage quick-create form if available" option turned on, and if the user clicks this button and selects one of the listed tables this brings up the Quick Create form for that table, and it is not being created in the context of a parent, and would be created as orphan records!

How can I remove this button, or at least remove those tables that I need to have created only in the context of a parent record?

[blackfincloud]

One thing that does work - outside of using the Classic Mode of App Management - is to use Make.Powerapps.com and then just remove the entity from the app.  That's basically the same thing as "unchecking" the box in the classic app management interface.  The problem is - as perhaps you are alluding to - that while the entity is indeed removed from the upper Global Create ribbon, the Quick Create forms stop working.  

This topic, I think, is a good one to add for suggestions, because it is an annoying oversight for people who want to be able to continue to use the Quick Create forms in the context of parents and want to avoid orphaned records. 

[Dave-Storey]

Hi, you are correct.  I said it "works perfectly" because it removed the table from the global command plus sign, but I just noticed that also causes the Quick Create form to no longer open when creating the record in the context of the parent.  Ugh, I will continue to use the JavaScript to prevent the form from opening from the global command bar, and re-add the table to my app so the Quick Create form will resume opening correctly.

[blackfincloud]

Thanks, Dave - yeah, we are looking at the same thing. I'm voting for your solution in this project  - so thanks for sharing it. We'll see what the client wants to do, but I think this is a fairly glaring shortcoming because a big reason for Quick Create, in my opinion, is to leverage mapping between parent and child fields - and they often go beyond just the parent record itself.  There are no less than six important fields that we rely on to map.  

It really needs to be a simple thing to do in the new ribbon management system to remove those entities without compromising the Quick Create capability.