Debugging the origin of a message in D365 F&O

Dynamics 365 ERP - Development

The article discusses scenarios in Dynamics 365 F&O where developers encounter warning or error messages that hinder certain functionalities.
Developers are responsible for finding the source of the messages and identifying any configurations that may affect the logic.
Messages displayed on the User Interface in Dynamics 365 F&O are dispatched using the Info class, which is part of the Application Platform model.
The info(), warning(), and error() global methods all utilize the Info class to show messages on the screen.
The add() method is the trigger point for adding messages to the Infolog, and a breakpoint can be set to debug when a message needs to be displayed.
The article provides an example of investigating an error message related to accessing 'Employee self service' and suggests modifying or configuring certain areas to resolve the issue.
The article emphasizes that the full stack trace of methods called to reach a certain point can be viewed in the Infolog, aiding in identifying where modifications or configurations need to be made.
The article concludes by highlighting the importance of being able to easily identify the origin of error messages and how it can help in situations where there is a lack of proper explanation.

Registered users can view the full text for FREE!