Dynamics Community Forum Thread Details

Best Practices for Structuring Plugins in Microsoft Dynamics for Performance and Maintainability

My issue is, lets say I have 20-25 entities, who all have some form of custom logic. One might have 1 single plugin, another might have 5.
I am trying to find resources on what Microsoft recommends according too performance, maintainability etc... for plugin development.

So far I have read this:
Optimize custom assembly development - Power Apps | Microsoft Learn
Which seems to suggest to have a single large assembly for all your plugins.

Which I do not agree with for our project, as it has far too many entities for it to continue being less than 16 MB.

What I cannot find information about, is how to structure the plugins you create.

To expand upon this, lets say we have a plugin which should trigger on five different fields.
Do we create a single plugin for each of these fields?
Do we create individual steps for each field for an update?
Do we create a single plugin, using the filtering attributes and handle the logic in there?

My reasoning or asking this, isn't that the case above is a serious issue, but rather that we sometimes have plugins that triggers on 45 different fields, and I am unsure how each of these solutions might affect our solution.

Quick Links