Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Solution import issue ...
Microsoft Dynamics CRM (Archived)

Solution import issue in trial instances

(0) ShareShare
ReportReport
Posted on by Community Member Microsoft Employee

Import-Issue.PNG

Hi,

I have setup two Dynamics CRM custom trial instances. Made configuration and customisation changes (Accounts to Organisation) in one instance and trying to export and import solution into another trial instance so to check if everything works fine. But getting above error -

Following components are missing in your system and are not included in the solution. Import or create all missing components and then try importing this solution again.

Managed Solution - msdynce_service (9.0.5.11)

I did search through the community and find an article on this solution  - https://community.dynamics.com/crm/f/117/t/269493,   but seems I could not delete or remove the All Organisation view from the solution.

Do I need to contact Microsoft on further help as this problem could potentially result in loss of development effort in future?

Thanks

AJ

*This post is locked for comments

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Solution import issue in trial instances

    EDIT: OK, i got it :-)

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Solution import issue in trial instances

    Spot on..

    Did a find and replace of old id with new id in both solutions and customisations xml files, imported and it worked fine!!

    Amazing fast response and quick solution, fabulous! should have tried community before!

    Thanks a lot!!!

  • Verified answer
    a33ik Profile Picture
    a33ik 84,323 Most Valuable Professional on at
    RE: Solution import issue in trial instances

    Hello,

    Check the last reply - it's a workaround to solve your issue:

    We just ran into the same issue.  It looks like the GUIDs for these 2 system views changed somewhere along the way.  As a workaround, I unzipped the solution and did a find/replace.  Afterwards, the solution import successfully.  Certainly not something we want to do every deployment, so I'm following up with Microsoft. 
    For posterity, here are the new/old GUIDs (from our instances):

    All Accounts
    - Old: B18E750A-857B-49C5-8C4E-851EBC857E24
    - New: 65FFAF9A-E8C5-432D-860B-32F841B00D87
    All Contacts
    - Old: 3A3D00E4-AD90-4AA3-B9AB-1E4F82900D29
    - New: 0D5D377B-5E7C-47B5-BAB1-A5CB8B4AC105

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,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans