#Define number sequence code
#Define number sequence series

For example, use this scope for the number sequence for the expense report number that is in the expense report table, TrvExpTable. Use the Legal entity scope when the underlying table does not include the DataAreaId field and has a foreign key to the legal entity table, CompanyInfo. Legal entity – A separate number sequence is used for each legal entity. If a number sequence has already been set up for a reference in one of the companies included in the virtual company, you must delete the existing number sequence before you can set up a number sequence for that reference in the virtual company. If you are using Microsoft Dynamics AX 2012 R3 or AX 2012 R2, the Company scope also includes virtual companies. For example, use this scope for the number sequence for the customer account number that is in the Customer table, CustTable. Use the Company scope when the underlying table includes the DataAreaId field. For more information about the shared scope, see Number sequence overview.Ĭompany – A separate number sequence is used for each company. The Shared scope is available only for some references. Shared – A single number sequence is used for all organizations. Number := NumberSequence.The available scopes depend on the reference that you are setting up a number sequence for. Gets and returns the next value in a NumberSequence object Number := NumberSequence.Current('MySequence',true)

Gets and returns the current value in a NumberSequence object NumberSequence.Delete('MySequence',true) If NumberSequence.Exists('MySequence', true) then Verifies whether a specific NumberSequence object exists, and if so, deletes it NumberSequence.Insert('M圜ompanySequence', 0, 1, true) // Creates a NumberSequence object that starts with the value '0', increments by '1', and is company-specific NumberSequence.Insert('StartsWithZeroIncrementTenSequence', 0, 10) // Creates a NumberSequence object that starts with the value '0' and increments by '10' NumberSequence.Insert('StartsWithTenSequence', 10) Creates a NumberSequence object that starts with the value '10' and increments by '1' NumberSequence.Insert('DefaultSequence') The value will not be returned on transaction rollback.Įxamples // Creates a NumberSequence object that starts with the value '0' and increments by '1' The value is retrieved out of transaction. Gets the current value from the number sequence, without doing any increment. Retrieves the next value from the number sequence. , )Ĭreates a number sequence in the database, with the given parameters.Ĭhecks whether a specific number sequence exists.

To create and manage number sequences, you use the NumberSequence data type and the following methods.

Creating and managing number sequences in AL

Customer cards, sales quotes, and warehouse activities are examples of entities that typically do not require continuous numbering. So, if there are no regulatory requirements for using continuous numbering, you can improve performance by allowing gaps and using a number sequence instead. This option actually uses number sequences in the underlying code, and allows you to implement non-continuous, non-blocking numbering.

#Define number sequence series

Number series also include an option called Allow Gaps in Nos. Using non-blocking number series for improved performance This can potentially block other users from being able to work.įor more information about number series, see Create Number Series in the Business Central application help. The drawback of using continuous numbers is that when a number is requested by a transaction, the No Series Line table in the database is locked until the transaction completes. This typically includes documents such as purchase orders, sales orders, and invoices. Unlike number sequences, number series are specially designed for scenarios where you have to use a continuous numbering system on transactional records. Number sequences and number series in the application These gaps, for example, can occur when transactions are rolled back or numbers are allocated but not used. This means that numbers used on records in tables can have gaps. Numbers are used sequentially, but numbers can be skipped. The numbers in a number sequence are generated in ascending order at a defined interval.

#Define number sequence code

Instead, the application code references the number sequence object and coordinates the values across records. Business Central number sequences are built on SQL Server sequences, which means that they are not associated with any tables.

In AL, you can create and manage number sequences that generate numeric identifiers for data and records. APPLIES TO: Business Central 2019 release wave 2 and later