I am here to explain one problem that I faced, when doing
import of a solution in Microsoft Dynamic 356 CRM environment. I got an
exception when I tried to import my managed solution from one Dynamic 356 CRM environment
to other newly instantiated one.
Before I promote my solution to Production instance, I wanted
to make sure that my solution is error free and there is no component dependency,
which usually one have faced during import of a solution.
So I decided to make a new test environment and do testing there
and if everything is working well, I can take further steps to move it to
production environment.
I did some of the changes in existing standard business
process flow like removing some of the fields and adding few as my client
business requirements. When I exported the solution both in managed and
un-managed formed, I did not receive any complaints from Dynamic CRM platform.
When I tried to import the managed solution to my new test
environment, the import wizard complains about below listed error.
Failed to import Business Process 'Lead
to Opportunity Sales Process' because solution does not include corresponding
Business Process entity 'leadtoopportunitysalesprocess'.
Failed to import Business Process
'Opportunity Sales Process' because solution does not include corresponding
Business Process entity 'opportunitysalesprocess'.
Solution:
We need to add corresponding entity to our solution, as we
did some changes in Standard out the box business process.
- These corresponding entities do not appear under standard entity list.
- They also don’t get added when you may try to add all required components.
- In fact, I found them under 1:N relationship of respective entity.
Here is a screen shot of an Opportunity Sales Process as a Related
entity which appear in 1:N relationship of Opportunity entity.
Similarly, we can add Lead to opportunity Sales Process
entity under 1:N relationship of Lead entity. Once we do this, we can see both
entities which were missing in above exception are listed in entities list of
solution.
After adding these entities, my import customization went successful.
