The content type "XXXX" is part of an application feature

Scenario :

SharePoint has the flexibility of storing data based on the content type, where the list can be associated with more than one content type. It means, a list can be used to store different templates of data. This is the main reason we leverage content type with SharePoint. Having said that, when you try to delete the content type, many of you might encountered an error reported by SharePoint, “The content type ‘XXXX’ is part of an application feature” and SP does not allows you to delete the content type. Scripting conquer the SharePoint UI way of deletion..? Apparently no, the same error is reported when you try to use the PowerShell to delete the content type.

Reason :

Due to a flag set internally into the content database, the content type is allowed to delete neither through UI nor programmatically.

Steps To Delete :

      1. In-order to delete the content type you should first remove any references with list instances. This can be inspected by the following script.

      2. You need to delete all lists which are reported by above script.

      3. Interestingly, though you delete those lists, the content type still reference to the deleted lists instances, which is residing inside the recycle bin. This has to be delete too.

         You have to make sure that you delete the list instance from both

·        End user Recycle bin

·        Deleted from end user recycle bin

       4. Once you have cleared the all the evidence of the list instance, you can go to the relevant content type feature, and de-activate it.

       5. Now your content type is automatically get deleted by feature de-activation process

Solution :

You should always remove the content type connection as I have shown you and then de-activate the content type feature to remove it.

Control Lead Qualification process in CRM 2013 - Refresh Page

Scenario :

You may not want to create account record or create opportunity record or both. I do not want to replicate the same content here . This article is very much informative but its lacking of giving comprehensive process to the end user. i.e : Once you have hooked the plugin up with the qualify lead message, the subsequent process is hindered. The page freezes and user does not realize the lead is qualified. This may end up with multiple clicks and multiple error messages, as the lead is already closed.

Solution :

1.             Follow up the article and bind the plugin for the qualify lead message.

2.             Write a javascript to show a notification to the user and reload the current record. My script is as follows :

function ShowQualifiedNotification(logicalNameOfEntitiy, recordId){

         Xrm.Utility.alertDialog("The selected lead is qualified",function(){Xrm.Utility.openEntityForm(logicalNameOfEntitiy, recordId)})

}

3.             Upload the above javascript as webresource.

4.             Install Ribbon work bench from here.

5.             On the form section, right click on Qualify, and click on Customize Command as below.

6.             Add a new step to the existing two commands, with a new javascript function you have written.

7.             Add CRM type parameter as above.

         8.     Publish the solution

Now once you clicked the qualify lead, you will get a notification and the record refreshes.