Skip to main content

#MSDyn365BC 2020 Wave 2 - Data Audit System Fields.

Hi Readers,

In this series of articles we will discuss about what's new in the product with Business Central 2020 Wave 2.

With Business Central 2020 Wave 2 (V17), Microsoft have added Data Audit System Fields in all Tables.

In this article we will understand what that means and how developers can utilize these fields with AL Programming.

#MSDyn365BC #BusinessCentral

With all tables, it means all - 

  • Base Microsoft Tables.
  • All Extension Tables.
  • Temporary Tables.
What are Audit System Fields added in every tables -
  • SystemCreatedBy
  • SystemCreatedOn
  • SystemLastModifiedBy
  • SystemLastModifiedOn

CreatedBy or ModifiedBy are GUID - Why?

When we create a New user in Business Central, a unique GUID is assigned to the user. 

GUID will never change for the use in Business Central. 

As a developer you can actually set a Lookup value based on GUID.

What These Fields are used for?
  • Used for Audit purpose. 
  • User cannot manually modify any of the audit Fields.
  • Developers cannot assign/modify values to any of the audit fields.
  • Platform sets these values.
  • Audit Fields cannot be imported with configuration packages.
How these Values are assigned?
  • After all onbefore[Modify|Insert] Events.
  • After the Modify/Insert Triggers.
  • Before all onafter [Modify|Insert] Events.
When New Records are Inserted?
  • SystemCreatedBy and SystemCreatedOn are populated with Values.
  • Fields SystemLastModifiedBy and SystemLastModifiedOn will be same.
When Records are Modified?
  • SystemLastModifiedBy & SystemLastModifedOn are updated.
  • No Impact on SystemCreatedBy and SystemCreatedOn.
What is there for Developers?
  • Developers can use these fields to filter records.
  • These Fields can be added in the page for user visibility.

Developer Usage - Example?

Example 1 - Add Fields in Page using Page Extension.

Example 2 - Use System Audit Fields in the code to filter Records.

Stay connected, We will discuss more about new features in product and how to use it.

Let me know your views as comment to this article.

Saurav Dhyani


Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

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.