Skip to main content

MSDYN365BC - Autoincrement Property With Extension Development.

Hi Readers,

Last week I was working on an Extension Development for a tool that I am developing and I was stuck with a issue related to Auto Increment Property.

So Here I am sharing that quick information with You.

Let's first understand what that property is and what is changed with Extension Development.

#MSDYN365BC, #AutoIncrement, #AL

AutoIncrement Property - 

If you set this property then the field value should be automatically incremented. I have seen this property to be used in Table Fields as primary key most of the time.

If a field with autoincrement property is set as primary key, you don't need to assign value to that field and it will automatically increment value when insert happens.

What Data Item it Applies to?
You can only set this property for Integer and BigInteger Data Type fields.

While using Remember
  • A table can only contain one auto-increment field. 
  • The AutoIncrement property does not work with Dynamics NAV temporary tables.
What Changed in AL or Extension Model?

In a New table that is part of your extension you can define AutoIncrement property in a field but you cannot define an AutoIncrement Field in Table Extension.

Why we cannot define in Table Extension? 

Since there could be multiple table extensions for a table, all installed at the same time on a tenant, and each of these could have added an AutoIncrement field, the decision was to block its use.

Auto Increment Field in New Tables?

In a New table that is part of your extension you can define AutoIncrement property in a field. 

References - 
So while converting your customs to AL Extension Model keep this in mind.

Regards,
Saurav Dhyani

Comments

  1. Not sure about it. I have such autoincrement field in BC365 ver.15 table and it works. That field is also part of composite primary key.
    /Related field in another table is showing a little bit strange behaviour, when records are not inserted yet (I have seen negative increments).

    ReplyDelete
    Replies
    1. Hi,
      Auto Increment Fields are allowed in New Tables but you cannot have AutoIncrement Field in Table Extension.

      Delete

Post a Comment

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.