Forum Discussion
SharePoint List Web Parts - New UX
The new list-title menu in the List web part is exposing SharePoint’s built-in New command even though your process uses a separate intake button. The supported control is view-level command-bar formatting. Open the source list, switch to the same public Calendar view used by the web part, choose the view menu > Format current view > Advanced mode, and add this at the root of the existing JSON: "commandBarProps":{"commands":[{"key":"new","hide":true}]}. Save, confirm the page web part uses that Calendar view, then republish and hard-refresh the page. Microsoft documents the new command key and hide property as valid for every view layout, including calendar. Merge this block with existing formatting rather than replacing it. This hides the creation command but does not remove Add Items permission. If users must be prevented from bypassing your intake process, apply list permissions that remove direct item creation; otherwise the formatting is only a user-interface control.
Hello,
When I hide the new button, my original button is now gone - as you noted. But, the issue is that the new button is still there and won't go away!^This is my list view within site contents after making the modification
^This is my list web part after making the modification
As you can see my original button is gone, but the "New Item" button has not disappeared.
Thank you for your assistance!I am not sure what mechanism you are using to add data to this list. For example, if you are using a List Form or any other way for data entry, I would recommend not granting Contribute or Edit permissions on the list to users.
If users only have Read access to the list, the New Item button will not be visible, preventing them from adding items directly to the list. This helps ensure that data is submitted only through the intended form rather than directly through the list interface.
It depends on the list, of course.
For this list - I am using the list form, and all users have the ability to Create Items, but they can only edit the items they've created.
This suggestion that you're providing isn't feasible, but thank you.
