It seems that there is a major bug in crm 2015 where I cannot update an existing solution which contains an activity entity if that solution/org was updated from 2011/2013.
The following are the steps I was able to replicate this issue in both scenarios, 2011 to 2015 and 2013 to 2015
1) Create solution Solution1 in Org1 on CRM 2011 deployment.
2) Add an activity entity to Solution1 on Org1.
3) Export Solution1 from Org1 as managed and import into Org2 on CRM 2011 deployment.
- ismapiprivate and leftvoicemail fields will be unmanaged.
4) Create backup of Org1 and Org2 on CRM 2011 deployment and restore both to CRM 2013 deployment.
5) Export Solution1 from Org1 on CRM 2013 and import into Org2 on CRM 2013.
- Import will fail with error ‘A managed solution cannot overwrite the Attribute component with Id=? which has an unmanaged base instance’.
- This is because the fields ismapiprivate and leftvoicemail are unmanaged in org and they are included in the solution file exported from CRM 2013.
- This can be resolved by manually deleting the ismapiprivate and leftvoicemail attributes from the Customizations.xml file before importing.
6) Create backup of Org2 on CRM 2013 and restore to CRM 2015.
7) Import Solution1 from Org1 on CRM 2013 to Org2 on CRM 2015.
- Import will fail with the following error.
- ‘A managed solution cannot overwrite the Attribute component with Id=d44da6b3-a096-e411-80c4-0003ff50363d which has an unmanaged base instance. The most likely scenario for this error is that an unmanaged solution has installed a new unmanaged Attribute component on the target system, and now a managed solution from the same publisher is trying to install that same Attribute component as managed. This will cause an invalid layering of solutions on the target system and is not allowed.’.
- It turns out that the field it’s complaining about is the processid field which is unmanaged in the org. However, that fields does not even exist in the Customizations.xml file!!!
- The processid field is a field that did not exist in CRM 2011 and although on new solutions created/imported in 2013 this fields would be automatically added it was not auto added when the org was restored to 2013. However, this field was automatically added as unmanaged to the org when the org was restored to CRM 2015.
8) Import Solution1 from Org1 on CRM 2013 to Org3 on CRM 2015.
- Import succeeds even without removing the ismapiprivate and leftvoicemail from the Customizations.xml. (Thanks to Microsoft fixing this issue).
- Ismapiprivate, leftvoicemail and processid will be managed.
9) Create solution Solution2 in Org3 on CRM 2013 deployment.
10) Add an activity entity to Solution2 on Org3.
11) Export Solution2 from Org3 as managed and import into Org4 on CRM 2013 deployment.
- processid field will be managed.
- traversedpath does not exist.
12) Create backup of Org4 CRM 2013 deployment and restore to CRM 2015 deployment.
- Traversedpath field was auto added as unmanaged.
13) Export Solution2 from Org3 on CRM 2013 and import into Org4 on CRM 2015.
- Import will fail with the following error;
- A managed solution cannot overwrite the Attribute component with Id=080c291f-c796-e411-80c4-0003ff50363d which has an unmanaged base instance. The most likely scenario for this error is that an unmanaged solution has installed a new unmanaged Attribute component on the target system, and now a managed solution from the same publisher is trying to install that same Attribute component as managed. This will cause an invalid layering of solutions on the target system and is not allowed.
- It turns out that the field it’s complaining about is the traversedpath field which is unmanaged in the org. However, that fields does not even exist in the Customizations.xml file!!!
- The traversedpath field is a field that did not exist in CRM 2013 and was automatically added as unmanaged to the org when the org was restored to CRM 2015.
----
CRM 2011 version = 5.0.9690.4150
CRM 2013 version = 6.1.0.581
CRM 2015 version = 7.0.0.3543
----
This is a major issue preventing us as an isv to release updates for our customers who are getting updated to CRM 2015. Any workaround would be appreciated. Otherwise a quick fix by Microsoft is really important.