Written by Xuan Luan for I-Net Dynamics
What is Database Logging?
Database logging is a feature that allows you to track specific changes to tables and fields. The feature is also available in AX2012 and there is not much of a difference in setting it up in Microsoft Dynamics 365 Financial Operations.
Some example cases of utilizing database logging that we have come across are
● Businesses that want to keep tracks of changes to specific tables. These tables might have sensitive information or serve their specific business requirements, of which they want to have auditable records of changes.
● Some companies want to monitor changes of users in systems. For example, they want to record employeess who have been added and removed from the system.
Database logging and performance:
The feature is useful in some scenarios; however, just a quick reminder, logging requires resources and meticulous management. It might lead to some performance impacts when you overuse it. Although this document about performance implications of database logging is for AX2012, the same applies to Microsoft Dynamics 365 Financial Operations.
How to set up database logging
In this blog, we will guide you step by step to set up database logging to tracks roles assigned to users in the system.
1. This should be set up by the Admin user. Only users with the System Administrator role can access the System administration module.
2. Navigate to the feature: Click System administration > Setup > Database log setup.
The database log setup form will be opened. You might find enabled logs here. If what you want is not already listed, you add it by clicking New.
3. Click New to start the Logging database changes wizard
4. In the next window, you should be able to find tables that you want to track. Please be noted that not all tables are displayed. You can see more by clicking on two checkboxes “Show all tables” and “Show table names” at the bottom, which helps you to find required tables faster.
5. After selecting the table Security User Role, you can set what fields and changes you need. Logging everything is time-consuming and redundant, you might filter the fields depending on your needs. Here for the demonstration purpose, I’ll select all the fields.
6. Clicking Next, in this window, you can select what types of changes to track. Changes that can be tracked include insert, update, delete, or rename key. Again, I select everything here.
7. Click Next and then Finish to save. You might have some popups reminding about performance impacts, choose Yes. After that, you should see info log of operation completed.
How to see logs
You can navigate to System administration > Inquiries > Database > Database log.
1. Let’s test our new database log by the roles of a user. Here, I’m the Admin user with below roles.
2. Let’s remove the role System tracing user
3. Go to the database log form to check. You can click Refresh to get the latest data and also, sort the table to see the results better.
4. You should see the record as below
5. Also, you might want to check more details of this action by selecting the row and choose History tab. To see the full details, please click on Show cumulative changes and then full details will be shown correctly as below.
We hope that this article has been helpful to understand how you might utilize the Database Logging feature in Dynamics 365 Financial Operations. Please look forward to our future articles about some tips and tricks of our products. If you are interested in exploring any of our products and services, please contact us here.
