Microsoft.sharepoint.spexception the content type is in use

Early I thought error occurred due to permission issue for different users, but now site collection admin user also getting this issue. And also I try to reproduce the issue by sending long group name, empty string in group name, same group name which gave for group 1, but the issue is not reproducing.

Anyone please give some alternate idea to reproduce the internal serve error in SharePoint Hosted app. Products 72 Special Topics 41 Video Hub Most Active Hubs Microsoft Teams.

Security, Compliance and Identity. Microsoft Edge Insider. Azure Databases. Your job will be done. Hope This helps : Thanks Amreesh. Monday, March 2, AM. Tony Testa www. Sunday, January 25, AM. Before you deactivate the feature you need to make sure that no items or lists are using the feature. Also make sure you that are not using the contenttypebinding element in your feature as that will also prevent you from deleting the content type.

Sunday, January 25, PM. Tony and Gary, I've checked the content type and it's not being used. What could be preventing it from being deleted? Thanks, Claudia. Monday, January 26, PM. Claudia, Have a look at this guidance by Vince Rothwell. Friday, January 30, AM. I'm having this same issue. There are definitely no lists using the content type and no other content types deriving from it.

It leaves behind my content type and when I try to delete it manually I get ' The content type "Custom Type" is part of an application feature. Any help would be awesome. Thanks, Joe. Thursday, February 12, PM. Active 1 year, 4 months ago. Viewed times. However, when I make the call I get the following error: , Microsoft. ViewQuery; console. Matthew Barben Matthew Barben 1 3 3 bronze badges.

I have been trying to figure out this error for the past few days and I have had 0 luck — BeerusDev. Add a comment. Active Oldest Votes. Mathieu Mathieu 2 2 silver badges 10 10 bronze badges. Sign up or log in Sign up using Google. An administrative user who has permission to manage lists applies the new content type to a list or document library, and it is in play.

Any user who is allowed to add items to the list can use your content type to create content. Administrative users can modify the content type to suit themselves by adding or removing columns, or changing other attributes. All of that is out of your hands. The key point, then, is that "creating" a content type really means creating a content type definition. A good content type definition anticipates how the content type is ultimately used.

You never create a content type from scratch. Instead, you always select an existing content type as the basis for any new content type that you create. This is exactly what Microsoft SharePoint Foundation does for its built-in content types. The website where a new content type is created must be in scope for the content type from which it is derived, so you should consider this when you write your content type definition.

For more information, see Content Type Scope. SharePoint Foundation supports a limited form of content type inheritance. When the Feature that defines a new content type is activated, columns and other metadata that are defined for the parent content type are passed on to the child content type.

This is the only part of inheritance that is automatic. In earlier versions of SharePoint Foundation, columns and metadata that were added to a content type after it was provisioned were not inherited by child content types. In SharePoint Foundation , this behavior has changed. You now have the option to include columns and metadata that users have added to the parent.

For more information, see the description of the Inherits attribute on the ContentType element. After a content type is made available and is being used, you or someone else can modify the definition for the parent content type, but that change is not automatically pushed down to derived content types. This aspect of inheritance must be initiated manually, either through the user interface or in custom code.

For more information, see Updating Child Content Types. However, content type inheritance does allow you to work with content types much as you would with derived classes.

For example, just as you can override properties of a base class, you can modify attributes that your content type derives from its parent content type. You can add, alter, or remove columns; specify different New , Edit , or Display forms; specify a different document template; and so on.

What this means, then, is that you can create base content types just as you create base classes in developing an application framework.

For example, you could define a content type named Financial Document with characteristics common to all financial documents in your organization. You could then use Financial Document as the basis for new content types, such as Invoice and Purchase Order.

The new content types inherit columns and other metadata from Financial Document, so you define common elements only once, on the parent content type. You can get ideas for building your own content type hierarchy by studying how SharePoint Foundation uses inherited attributes of base content types, and how it modifies them.

A good place to start is with the content type gallery in the user interface. On the Site Actions menu, select Site Settings. On the Site Settings page, under Galleries , click Site content types.

On the Site Content Types page, click the link for an interesting content type.