web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

Read option in Audit log

(0) ShareShare
ReportReport
Posted on by 182

Hi experts,

I have a requirement to get the Audit log of GL transactions. I know we can enable the the log in system administration and  can track Insert, Update, Delete and Rename key option.

Is there any possible way that we can track log View option also. I couldn't find any documentation related to read option.

If there is no option, is it ideal to develop a custom log functionality which tracks all logs related to GL.

Thank you

Pavan

I have the same question (0)
  • Verified answer
    nmaenpaa Profile Picture
    101,160 Moderator on at

    It's not possible to track who has read your transactions. And I don't think that it's necessary for the auditor, either.

    Instead you can provide a list of users who have access (via security roles) to read this information.

    Developing some functionality around it would be quite difficult, since you would need to cover D365 forms, data entities, Financial Reporting and custom services in order to capture all scenarios where someone might read data from the database. And if you use BYODB or other external solution for data export & analysis, then you would need to develop some way to log the read operations in those systems as well.

  • André Arnaud de Calavon Profile Picture
    301,069 Super User 2025 Season 2 on at

    Hi Paven,

    I never heard of this requirement before on GL transactions. It would be a customization anyway.

    Can you tell if it is about certain transactions only or all transactions? Usually when somebody is not allowed to view transactions, you can restrict access to the form using security configuration. If it is about certain transactions, you can also consider eXtensible Data Security to restrict access on data.

  • Maverick Profile Picture
    182 on at

    Yes, Andre it is for all GL transactions

  • Suggested answer
    nmaenpaa Profile Picture
    101,160 Moderator on at

    There's a good reason why the read operations can't be tracked. That would have a HUGE performance impact, because it would turn every "read" operation in "write" (since you would need to write the log).

    For example if user fetches 100 journal lines, the log would need to write 100 log lines (so that you could see which lines the user has seen).

    If some user prints a report that shows 100 000 transactions, the system would need to write 100 000 lines of log.

    Anyway, did you discuss with the auditor? Do they really require this? Or are they happy if they get a list of users who have read access to the data?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 592 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 478 Super User 2025 Season 2

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 305 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans