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

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

RTC Report It is not possible to instantiate the Visual Studio bridge.

Hi all, As a Navision developers I have Multiple Versions of Navision running in single Machine. As discussed Earlier in the post how to run multiple Version of RTC in single machine. So my machine have following details for RTC Versions - NAV 2009 R2    - is installed. NAV 2009 SP1  - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\ NAV 2009         - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 IN\ This approach has been working great for execution of Classic and RTC Clients. However, after installing Dynamics NAV 2009 R2, if i tried to view the Layout for an NAV 2009 SP1 Report i was getting the following error: ---------------------------  Microsoft Dynamics NAV Classic  ---------------------------  It is not possible to instantiate  the Visual Studio bridge.  ---------------------------  OK    --------------------------- After searchi...

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.