Skip to main content

Notifications

Microsoft Dynamics 365 | Integration, Dataverse...
Suggested answer

One C# File per step or per message/entity for plugins?

Posted on by 22

Hi guys. Currently our plugin assembly is structured in the following way. PostUpdateWorkorder.cs, PreUpdateWorkorder.cs, PreValidateUpdateWorkorder.cs, PostCreateWorkorder etc...all inside of the assembly. This follows on for all of our entities. We find ourselves having a lot of bugs within plugins, such as awkward loops and weird fixes to small issues. Should we have one file per entity that contains an execution method for all of the different messages (post, pre, prevalidate) or continute to do it the current way?

  • Suggested answer
    a33ik Profile Picture
    a33ik 84,323 Most Valuable Professional on at
    RE: One C# File per step or per message/entity for plugins?

    Hello,

    I would recommend having one plugin per scenario.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Complete!

🔔 Be sure to subscribe to the new forums you are interested in to stay up to date! 🔔

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,113 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 229,918 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans