Dynamics 365 ERP - Development
Category
Apr 24, 2024
Published date
Text
Article Type
AI Summary
- The article discusses the use of data events in Dynamics 365 Finance and Operations to create an external audit log.
- The problem that motivated the development of this solution was the need for a comprehensive audit history of data modifications in the system, especially for essential business entities.
- The limitations of the built-in Database log feature in Dynamics 365 Finance and Operations made it unsuitable for the client's needs, as it only tracks changes in the primary table and is stored in the same database as the operational data.
- The solution proposed in the article involves using data events to capture data changes and send them to an external service or database for storage.
- This solution offers several benefits, including the ability to track changes in any entity, store old and new values of changed fields, and provide a secure and scalable audit log outside of Dynamics 365 Finance and Operations.
- The architecture of the solution includes components such as data events, Azure Event Grid, Azure Function, and Cosmos DB.
- The data flow starts with a data change in Dynamics 365 Finance and Operations triggering a data event, which is then sent to the Azure Event Grid and processed by the Azure Function before being stored in Cosmos DB.
- The development process involved configuring the Event Grid as an endpoint in Dynamics 365 Finance and Operations, creating a Cosmos DB and container, and dealing with challenges related to data conversion and library compatibility.Overall, the article provides a detailed explanation of the problem, solution, architecture, and development process related to using data events for creating an external audit log in Dynamics 365 Finance and Operations.
Registered users can view the full text for FREE!
Sign In Now!