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, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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
As part of preparing our organisation for its first Major Upgrade, I thought it would probably be a good idea to get a list of all dependencies we had from our Plugins to help assist us with a test plan.
This should have been reasonably simple. Each Plugin Assembly contains a bunch of plugin types, in total we have hundreds of plugin types and when we click on each one we can see the dependencies for them. Because they are contained within a Plugin Assembly you might assume that you can see all the dependencies of the plugin types within the Plugin Assembly container.
Apparently not. The plugin assemblies themselves report NO dependencies even though it contains plugin types which contain dependencies. Adding all of the plugin assemblies into a Solution and reviewing the dependencies there also ends up with the same result.
Getting a list of dependencies for plugins should be a simple operation, we have been unable to do this within the front end of Dynamics. Using C# and the RetrieveDependentComponentsRequest against a list of plugin types also doesn't appear to play ball.
The only way we have been able to find to get the dependencies for our plugins is literally by clicking on each plugin type and clicking show dependencies. I'm not planning on doing this, there must be a better way.
Does anyone have any suggestions or experiences which are similar?
The message steps that use a plugin are stored in the metadata of the organisation / instance. Looking at the code we use to detach a plugin's message step from a entity I can see why as the code has 4 individual metadata enquiries to identify the guid of the appropriate message before we delete it.
The following will give you the name of the entity attached to a plugin - you will need to add a filter in the condition part below as (especially in 9.0) there are a lot of Microsoft internal plugins that appear in the list that don't appear within the plugin registration tool...
<entity name="sdkmessageprocessingstep" >
<link-entity name="plugintype" from="plugintypeid" to="plugintypeid" >
<attribute name="name" />
<attribute name="assemblyname" />
<condition attribute="name" operator="begins-with" value="1st part of the Plugin's Name" />
<link-entity name="sdkmessagefilter" from="sdkmessagefilterid" to="sdkmessagefilterid" >
<attribute name="primaryobjecttypecode" alias="entity" />
Business Applications communities