Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Dynamics 365 solution ...
Microsoft Dynamics CRM (Archived)

Dynamics 365 solution import issues

(0) ShareShare
ReportReport
Posted on by David Reinh

Hi all

I wanted to sound out the community on whether anyone is experiencing similar issues to myself. I'm trying to export a pair of solutions from CRM 2016 online into a Dynamics 365 trial (setup for sales). The solutions are working fine in 2016 and, as recently as last week, imported into a CRM 2016 trial with no problems. One covers customizations for accounts and contacts, the second covers customizations on leads and opportunities.

I tried simply exporting the solutions from 2016 online and importing them into Dynamics 365. On import, I've received a number of dependency issues, some of these were to do with other things that were in the Dynamics 2016 environment (Field Service, Project Service) but I isolated those, cleared them out of the solutions and have been able to successfully import into Dynamics 365.

Since then, I have experienced:

  • The solutions in Dynamics 365 have ALL the forms, not just the customized forms. I cannot remove the system forms and they introduced a whole series of dependencies. To work around this, I created new solutions within the Dynamics 365 trial and added all the customizations (effectively rebuilt the solutions).
  • I exported these and imported them into a second Dynamics 365 trial environment and learnt that all option set values have been reset in this process. I went back to the source solution (2016 online) and the option set values are definitely customized. I looked in the first D365 environment and the option set values are not customised. So they seem to have been wiped out on import into D365.
  • In the solution XML (of the solution file exported from the first D365 trial), there are some missing dependencies which I cannot find. The solution imported into the second D365 trial environment with no problems though.

In summary

  • Solutions imported into a D365 (trial) environment have all the system forms, not just the customized ones, and so have a series of unnecessary dependencies 
  • Option set values seem to be cleared out on import into D365

Note - all of this has been done with unmanaged solutions as we need to be able to evolve the solution once it is in D365.

Has anyone had any similar issues?

Thanks

David

*This post is locked for comments

  • David Reinh Profile Picture
    David Reinh on at
    RE: Dynamics 365 solution import issues

    Hey Rafael

    Eventually we built new versions of the solutions in a D365 environment and that solved most things.

    Your error looks like a security role / permissions error. We did see that a number of the new features have new security "rows" in the security role table. (That's not the best description I've ever seen, but I'm talking about the area where you specify security roles). If you're using custom security roles, it might worth looking to see if those roles need some permissions added for new items appearing in the security role setup that weren't there in CRM Online.

    Thanks

    David

  • Rafael Batista Profile Picture
    Rafael Batista on at
    RE: Dynamics 365 solution import issues

    Hello David,

    I am facing the exactly same problem as you when trying to import a CRM solution into D365. The importation worked well on the my D365 preview trial, but I have some strage errors when importing on a standart D365 trial.

    These errors are something like :

    <result result="failure" errorcode="0x80040220" errortext="Principal user (Id=2a05fe3a-723a-4556-8fed-0f408c1df8ba, type=8) is missing prvCreateCustomControlDefaultConfig privilege (Id=481f2478-dcd7-4145-9aec-ab1e789ccdc9)" datetime="14:19:49.50" datetimeticks="636154211895062161" />

    Have you had the samed kind of dependencies ? If yes, how have you manage to resolve them ?

    Best regards,

  • Verified answer
    David Reinh Profile Picture
    David Reinh on at
    RE: Dynamics 365 solution import issues

    UPDATE: It seems that option set values have been maintained (in the first D365 instance), however (in some cases) the data value (i.e. the internal reference number) has been changed. This invalidates all my datamaps but means I don't need to redo customizations. I've looked at a few fields in the second D365 instance and these seem okay as well, I've not yet done a thorough check of all fields.

  • David Reinh Profile Picture
    David Reinh on at
    RE: Dynamics 365 solution import issues

    That's right. The original solution in the CRM 2016 environment only includes the customised components.

  • Suggested answer
    razdynamics Profile Picture
    razdynamics 17,304 User Group Leader on at
    RE: Dynamics 365 solution import issues

    Hi David, So just to clarify when you built your solutions did you only include the customised components into the solution, and definitely did not included the system objects into your solution before you exported it?

    Best Wishes, Raz

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