Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
we've encountred an issue this morning trying to import a solution to our production instance.
After installing the solution we received the following error :
The import failed. For more information, see the related error messages. : Microsoft.Crm.BusinessEntities.CrmObjectNotFoundException: sdkmessageprocessingstep With Id = 5788b2c6-10f4-e911-a813-000d3ab8d7df Does Not Exist
I ignored the error and retry to import it once again, everything went will but after checking, we discovered that all workflows and business rules have been deactivated.
so we had to manually activate all our components.
to make sure we did the same in another environement and the same thing happend.
Any thoughts guys on the source of this problem ?
PS : we recently did the following configurations :
- Disable one of our developers licence
- Change the scope of a business rule from All-forms to a specified form
- Change the ownership of a workflow
The error says that plugin steps is missing in the solution , have you deleted any steps from solution before export?
Do you have any lookup reference in the business rules ?, This can be happen if you have any lookup reference but the same lookup reference not exists in the target instance.
In the import options see whether you checked options "Check to Enable any SDK message processing steps included in the solution". By default dynamics crm will not change the activated/deactivated state of an existing process.
Hi we opened a case at MS for the same issue. It was a product issue and it is supposed to be fixed by now.
We have not deleted any of our steps before export, and we do not use lookups in our business rules.
YES, we checked the option you mentioned.
Just for your information, we successfully imported the same solution a few days ago to the test instance.
Was that a long time ago or recently?
I have heard that this is a product problem, but unfortunately, I can't find it anywhere...
Business Applications communities