Breaking news from around the world
Get the Bing + MSN extension
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
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
I have made some changes in my code, but nothing spectacular and has nothing to do with the parameters of the workflow.
Suddenly I get this error message everytime I execute the workflow:
Unexpected exception from plug-in (Execute): My.Assembly.WorkflowStep: System.ArgumentException: The values provided for the root activity's arguments did not satisfy the root activity's requirements: 'WorkflowStep': The following keys from the input dictionary do not map to arguments and must be removed: workflow. Please note that argument names are case sensitive. Parameter name: rootArgumentValues
I can't find any argument named "workflow" so I assume this failure has nothing to do with my code.
Thanks for your help.
can you share some piece of code? did you try to increment the assembly version (for example from 188.8.131.52 to 184.108.40.206) before register the new version?
100% sure that the in and out arguments didn't change?
in and out arguments didn't change at all.
I have changed the version and checked, that the newer one is used.
Still the same error :(
well, without understating what changes you done to your code is difficult to check.
You can always create a brand new assembly (diffferent namespace) with the same new code and check if you get the same error or not.
You brought a good idea. With a new class name, it works !!
So it is definitely a CRM bug, isn't it ?
Sometimes it helps to change the friendly name in the plugin registration tool and afterwards reset the iis. This usually works for me.
I know, I am a bit late to answer this, above error pops up only in case, if you had an input or parameter in your workflow and registered same in crm. Then while updating it, you removed the parameters and updated the assembly in CRM and tried calling it in MS CRM.
So, what you just have to do is, go to the system workflow--> deactivate it-->remove and add your assembly reference again-->activate and voila!! it will work as you wanted
Business Applications communities