cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot import a solution in CRM 2016 with an entity that is email enabled

Author Name: SEAN TREVITT

When trying to import a solution that includes an entity that is e-mail enabled in CRM 2016, the solution import fails. The error that is reported by CRM references a field that is added in the 2013 upgrade from 2011, sendermailboxid.

The issue is as follows:
- Upgrading from 2011 to 2013 adds an attribute to one of our custom entities called sendermailboxid.
- If you export a solution with that entity in 2013 and then import the same solution, that succeeds with no errors.
- When the org is upgraded to 2015, if you export the solution with that entity and then import the same solution, that succeeds with no errors.
- When the org is upgraded to 2016, if you export the solution with that entity and then import the same solution, you get this error:
Invalid name for attribute sendermailboxid.
Custom attribute names must start with a valid customization prefix. k
The prefix for a solution component should match the prefix that is specified for the publisher of the solution.

Status: New
Comments
Level: Powered On
Status changed to: New
 
Level: Powered On

Did you find a solution for this issue?