New command: Remove content type from site
See original GitHub issueRemove content type from site
command: spo contenttype remove -u|--webUrl <webUrl> --contentTypeId <contentTypeId> --confirm
- webUrl: URL of the site from which to remove content type
- contentTypeId: ID of the content type to remove from site
- confirm: Don’t prompt for confirming removing the content type from site
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:10 (10 by maintainers)
Top Results From Across the Web
SharePoint Online: Delete a Content Type using PowerShell
Under the Site Content Types page, click on the name of the content type you wish to delete. Click on the “Delete this...
Read more >SharePoint Online: Remove site content type using PowerShell
1. Navigate to Site>Site settings > Content types. or. Enter the URL of the site where you want to remove the content type....
Read more >SharePoint 2013 - How to remove content type from library
You need to associate the library with another content type first. For example, Document. Make the new content type the "Default" and then...
Read more >Create, Retrieve Or Delete Site Content Type On SharePoint ...
In this article, you will learn how we can create, retrieve and delete site content types on SharePoint sites, using PnP PowerShell.
Read more >Delete Site Content Type in SharePoint using PowerShell
The example in this topic show how to use PowerShell to Delete Site Content Type in SharePoint. Using PnP (Pattern and Practice) PowerShell...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@waldekmastykarz it looks like this is a duplicate of #904 which has since been resolved.
Thanks @waldekmastykarz