Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
In the previous post, I described the business problem of logging and handling implementation level exceptions. In this post, I would like to suggest a solution.
Before you continue reading, note that logging implementation level exceptions is up to your code developer. Although the solution supplies easy methods to log exceptions (to be demonstrated in part 3), nothing will be logged If your custom code does not use the solution components.
Let’s start by defining some business requirements for the suggested solution:
Next, here are the suggested solution major components along with some architecture consideration:
The Exception entity will have the following attributes:
Finally, a nice diagram of the solution’s major components:
Feel free to comment on the architecture and the planned Implementation, I welcome your feedback.
In the next post I will describe the actual Solution and will demonstrate common usage scenarios.
Business Applications communities