Dynamics365 Chronicles

In the realm of Dynamics 365 CE customisation, specific client requirements often demand tailored solutions. Recently, a client approached us with a nuanced request: they wanted the Reported On (Custom) field of Case record to be dynamically set based on the creation method—either OOB Created On if case is created manually by the user or Created On of the parent Email Activity if the Case is created using 'Convert to Case' option from an Email activity. To achieve this precise functionality, numerous approaches exist. However, the most robust method involves the creation of a custom Plugin. This post serves as a guide detailing the steps to implement a Plugin in Dynamics 365 CE that fulfills this specific client requirement. The primary strategy involves writing a custom Plugin registered at the Pre-Operation stage for the Create message of the Incident entity. This stage ensures access to essential attributes before data persistence in the database. I am assuming that you are

Issue :  I created an Unmanaged Solution with prefix "fz" and then created a model drive app inside that solution. When I publish my app (or Publish All Customisation from the solution), the model driven app on the environment landing page does not show the publisher name as the one I created. It shows the publisher name as the name of the root (default) organisation unit. Explanation: Looks like the custom prefix is correctly applied to the modeldrivenapps in the unmanaged solution in this case. Just that the app icon on the environment landing page incorrectly displays the Default Publisher as the name of the root (default) organisation unit. To check if your custom publisher name is correctly prefixed with your app name, navigate to the app editing page and expand the right panel that shows the app name, description and other settings of app.  Expand the Advance Settings link and check the Unique name of the app. If it has the correct prefix then this mean that your model

Field service operations can be complex and one of the biggest challenges faced by businesses in this space is managing costs. That's where the new Not-To-Exceed feature in Dynamics 365 Field Service comes in. This feature allows you to set a limit on the cost of a service call, giving you greater control over your service delivery costs and helping you stay profitable. What is the Not-To-Exceed Feature? The Not-To-Exceed feature is a new addition to Dynamics 365 Field Service that allows you to set a limit on the cost of a work order. You can specify a maximum amount that you are willing to spend on a job, and if the cost of the job exceeds this limit, the system will automatically alert you and prompt you to take action. How Does the Not-To-Exceed  Feature Work? The Not-To-Exceed feature works by setting a limit on the cost of a work order. You can specify the limit when you create a new work order, or you can update an existing work order to include the limit. The system w