Skip to main content

Business Central v29: Use System Audit Fields in Analysis Mode and Profiles

Hi Readers,

Microsoft Dynamics 365 Business Central v29 introduces support for system audit fields in Analysis Mode and Profile customizations. This enhancement allows administrators to expose important audit information such as who created a record and when it was modified without building custom page extensions.


What Are System Audit Fields in Business Central?

System audit fields are automatically maintained by Business Central to track record creation and modification activities.

Common system audit fields include:

  • System Created At
  • System Created By
  • System Modified At
  • System Modified By

These fields provide valuable visibility into record history and help administrators, support teams, auditors, and consultants understand how data changes over time.

Why Were Audit Fields Difficult to Use Before v29?

Before Business Central v29, system audit fields were maintained by the platform but had limited accessibility.

Specifically, these fields were not available in:

  • Analysis Mode
  • Profile customizations
  • Personalization experiences

As a result, organizations often relied on custom page extensions to display audit information on pages.

While functional, this approach introduced additional development effort, testing cycles, deployment requirements, and long-term maintenance costs.

What Changed in Business Central v29?

Business Central v29 removes a major limitation by making system audit fields available in Analysis Mode and Profile customizations.

This means administrators can expose audit information without writing code or deploying custom extensions.

The enhancement provides a more configuration-driven approach and reduces the need for development resources.

How Do System Audit Fields Help in Analysis Mode?

Analysis Mode is designed to help users explore and analyze data directly from list pages.

With audit fields available, users can now:

  • Analyze records by creator
  • Review recently modified records
  • Track ownership trends
  • Identify operational activity patterns
  • Improve troubleshooting processes

This additional visibility makes Analysis Mode even more valuable for operational reporting and support activities.

How Can Profiles Use System Audit Fields?

Profiles allow administrators to define experiences for different user roles.

By including audit fields within profile customizations, organizations can:

  • Standardize page layouts
  • Expose audit information to targeted user groups
  • Eliminate unnecessary page extensions
  • Improve consistency across departments

This approach aligns with Microsoft's continued focus on low-code and configuration-first administration.

Why Is This Enhancement Important for Administrators?

Many organizations create customizations simply to display audit-related information.

With v29, administrators can accomplish the same goal through configuration.

Key advantages include:

Reduced Customization Footprint

Fewer extensions mean lower maintenance costs and simpler upgrade paths.

Better Audit Visibility

Users gain access to important record history information without additional development.

Faster Deployments

Configuration changes can often be implemented more quickly than custom development projects.

Improved Supportability

Support teams can access audit information directly when investigating issues.

Best Practices for Using Audit Fields

When implementing this feature, consider the following recommendations:

  1. Include audit fields only where they provide business value.
  2. Use Profiles to standardize visibility across user roles.
  3. Leverage Analysis Mode for operational investigations.
  4. Review existing customizations that may no longer be required.
  5. Document profile changes as part of governance processes.

Frequently Asked Questions

Are system audit fields available in Business Central v28?

No. System audit fields were not available in Analysis Mode or Profile customizations prior to v29.

Do I still need page extensions to display audit fields?

In many scenarios, no. Business Central v29 allows administrators to expose these fields through Analysis Mode and Profiles.

Which audit fields are included?

Examples include System Created At, System Created By, System Modified At, and System Modified By.

Are these fields available through personalization?

This enhancement focuses on Analysis Mode and Profiles. Personalization availability should be verified based on the specific page and release behavior.

Who benefits most from this feature?

Administrators, consultants, support teams, auditors, and power users who regularly investigate record history and data changes.


Final Thoughts

The ability to use system audit fields in Analysis Mode and Profiles is a practical but impactful enhancement in Business Central v29. By reducing dependency on page extensions, organizations can simplify administration, improve audit visibility, and maintain cleaner environments.

Subscribe to the Saurav Dhyani YouTube channel for Business Central technical tutorials, AL development, APIs, extensions, new features, and practical implementation guidance.

You can also connect with me on: 

LinkedIn

YouTube 

Regards,

Saurav Dhyani

Comments

Popular posts from this blog

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.

🚀 Exploring Vibe Coding with GitHub Copilot for Business Central.

Hi All, In a recent #BCOpenDiscussion session, we delved into the fascinating concept of Vibe Coding —a new way of building software where developers collaborate with AI (like GitHub Copilot) to co-create solutions.  The session covered practical setup, how AI understands context, and even touched on Microsoft's new Model Context Protocol (MCP) integration for enhanced learning. Let’s break down the journey, step by step.