Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics CRM (Archived)

sendermailboxId field on custom activity entity makes Solution import fail

Posted on by 69 User Group Leader

My CRM 2016 On-prem instance contains a custom activity entity "Special Request" that was created in CRM in ver. 2011.
We upgraded from 2011 to 2013, then to 2015, and 2016.
When I export the "Special Request" custom activity as part of a Solution, that Solution cannot be imported into another Organization.
The solution import fails on the field "sendermailboxid". Error message: "Invalid name for field 'sendermailboxid'. Custom field names must start with a valid customization prefix. The prefix for a solution component should match the prefix that is specified for the publisher of the solution."
Note:
-Customized activities were introduced in CRM 2011.
-The Mailbox entity was introduced in CRM2013.
-The sendermailboxid field was added in the 2013 upgrade.

I cannot delete the "sendermailboxid" field from the entity because it was added by the system as a standard activity field.
I cannot delete this custom activity entity "Special Request" because it is now part of the Default Solution.
I can create new custom activity type entities in 2016 that when exported in a solution, can successfully be imported into different organizations.

How can I get rid of this entity so I can recreate it as a new entity without the problems from being a 2011 holdover?

*This post is locked for comments

  • Allie_B Profile Picture
    Allie_B 69 User Group Leader on at
    RE: sendermailboxId field on custom activity entity makes Solution import fail

    You are right, this should be a bug since the 'sendermailboxid' is a system-created field for any custom entity. I am going to try this; THANKS so much!

  • Verified answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: sendermailboxId field on custom activity entity makes Solution import fail

    Hi Allie_B,

    I'll start by saying that the following approach seems to work BUT is not supported by Microsoft.  I'm working in a CRM environment that has been through a similar upgrade path as yours and experienced the exact same issue.  To fix this, I unpacked the exported solution file and modified the 'sendermailboxid' attribute in my custom activity entity (in your case "Special Request", and there could be multiple custom activities which may be impacted) and changed the <IsCustomField> node from 1 to 0 in customizations.xml.  So you end up with <IsCustomField>0</IsCustomField>.  I then saved the customizations.xml file, zipped up all of the files and imported this to a new CRM instance (where it failed previously), and it all seems to have worked.

    As a technicality, this seems to be a bug, as the 'sendermailboxid' attribute is not actually a "custom" field...it is added by the CRM platform during the upgrade process and I don't believe we are given any choice about this.

    I will finish by saying again, this approach is not supported and may have unintended consequences, but it does seem to get around the import failure you experienced.

    All the best!

    Andrew

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans