BeyondERP.Newsletter
Menu

Setup step on the User log page · System administration

Agree how long sign-in records are kept

Use this page to review user sign-ins and to clean up log records older than an agreed limit.

Used by
Security administrator
Business process
Administer system features
Menu item
SysUserLog
Main table
SysUserLog
Setup steps
1 on this page
Show what matters for
SETUP GUIDEHow to set it up8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isAn inquiry page that keeps an audit log of the users who have signed in.
What you do hereUse this page to review user sign-ins and to clean up old log records.
ExampleFor example, during an access review an auditor asks who signed in last month; the administrator filters the User log on the user IDs in question, then cleans up entries older than the agreed History limit (days).
User log page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

Setup steps on this page

Agree how long sign-in records are kept

Use this page to review user sign-ins and to clean up log records older than an agreed limit.

Steps from Microsoft

  1. Go to System administration > Inquiries > User log.
  2. Select Clean up.
  3. In the History limit (days) field, enter how old records must be before they're deleted.
  4. Select Select and choose the users, and optionally dates and times, to clean up.
  5. Select OK to run the cleanup once, or use the Batch tab to run it regularly.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExample
History limit (days)Only log records older than this number of days are deleted when you clean up.Microsoft Learn 90

Common errors and fixes

MessageWhat to do
An audit asks for sign-ins that are no longer in the logA cleanup with a short History limit (days) removed them. Agree a retention with audit before you clean up, and run the cleanup as a batch job with that limit. Microsoft Learn

Test checklist

  1. Sign in as a test user, then open User log and check that a row for that user and time is listed.
  2. Select Clean up, set History limit (days) to the agreed retention and choose a test user.
  3. Run the cleanup and check that only that user's rows older than the limit are gone.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Agree how long sign-in records are keptSet History limit (days) to the retention your auditors require and run User log cleanup as a recurring batch job with that limitCleanup deletes only records older than History limit (days); a fixed limit in a recurring job keeps the log to the retention audit needs.How long are sign-in records kept?Cleaning up with a small History limit (days) just before an audit, which deletes the sign-in records the audit asks for.Test: User log cleanup keeps records inside the history limit

Feature management and licence

Licence or add-inOn this system the page opens for Security administrator. Security administrators use it for sign-in audits. No Feature management feature needs to be turned on for this page.

Microsoft Learn

Solution architect

5Design impact

Shared or per companyShared: the same records are used by every legal entity. Microsoft data model
Can it be undoneOne-way: Deleted user log records can't be restored.
If you change it laterCleaning up the user log permanently deletes the selected sign-in records. The User log cleanup page can keep log entries of users with access to sensitive data separately from the rest. Microsoft Learn
Technical architect

6Technical

Menu itemSysUserLog Checked in Dynamics 365
FormSysUserLog Checked in Dynamics 365
TableSysUserLogShown as “User log” in Record infoKey field: Type, UserId, Computername, ClientType, BuildNum, SessionId, TerminatedOkChecked in Dynamics 365
Who can open itPrivilegesView user log SysUserLogViewDutiesMaintain security settings SysSecSecurityMaintain
1 security roleSecurity administrator SysSecSecurityAdministrator
Checked in Dynamics 365
Roles to set it up and use itTo use itSecurity administrator SysSecSecurityAdministratorGive people one of these roles. On this system, 1 role can open this page.Checked in Dynamics 365
Actions on the pageOptions: Personalize, Page options, Edit, ShareChecked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=SysUserLog
Data migrationLoad order: User log has no data entity in Data management, so it can't be loaded from a file or a configuration template. The log is written by the system as users sign in, so it starts empty in each environment.Checked in Dynamics 365
Table definitionSysUserLog columns and relations Microsoft data model
Everyone

8Sources