Against the background of the changes illustrated in the previous blog post, I logged the following tables/fields that are in my opinion the ones that should – from a financial perspective – be tracked at a minimum.

Fixed Assets
Setup section

Fixed AssetsValue modelsFixed asset identifiers (if used)

Inventory
Setup section

Items

Accounts Payable
Setup sectionVendors

Accounts Receivable
Setup sectionCustomers

Cash and bank management
Setup sectionBank accounts

General Ledger
Setup section

Please note that the previously illustrated tables that should get logged from a financial perspective represent my opinion. This selection is not meant to be exhaustive nor definite and aims to provide you with a starting point for setting up the database log.

Please also note that you should avoid logging transaction tables as logging them might have a negative effect on system performance.

If you miss important tables/fields that should be logged in any Dynamics AX setup and country-environment, feel free to leave a comment on this site to help other Dynamics AX users getting their setup right.

If you ever used the Dynamics AX database log you might have realized that it can be pretty hard to find the correct tables and fields that you need to log. One of the underlying reasons for those difficulties is that the elements that you can find in the database log window use labels that differ from the names that you can find in the AOT. Due to the use of labels, some of the elements that you want to have tracked do even appear double in the database log setup window (see the following screenshot for an example).
To overcome this issue and to alleviate the identification of the correct tables and fields that should be logged from a financial perspective, I made the following changes:

1. The first change made ensures that the AOT table names rather than labels are referred to. This can be realized by making the following adjustment (see the next screenshots).
Through the changes illustrated in the previous two screens, I ensure that the ConfigKeyLabels refer to names rather than labels.

2. The second change that I made is including the AOT name in addition to the label name in the Logsetup section of the database logging wizardThis change allows identifying the AOT table names and the original labels used and helps ensuring that the correct tables and fields get logged.