Skip to main content

What can go wrong with number sequences?

  • Very low performance of the application

  • Data base blocking on the number sequence table so al user get stocked when the need a sequence number.

  • Let’s start with the worst performance setup related to a number sequence. We set the customer account number on continues. The below table shows the queries that are executed.


    Continues = true, pre allocation = false
    First time (8 database calls)
    SQL statement: (SysRecordTemplateTable)

    SQL statement: (CustFormletterParameters)

    SQL statement: (NumberSequenceReference)

    SQL statement: (NumberSequenceTable)

    SQL statement: (NumberSequenceTable)

    SQL statement: (NumberSequenceList)

    SQL statement: (NumberSequenceList)

    SQL statement: (NumberSequenceTable)
    Second time (5 database calls)
    SQL statement: (NumberSequenceTable)

    SQL statement: (NumberSequenceTable)

    SQL statement: (NumberSequenceList)

    SQL statement: (NumberSequenceList)

    SQL statement: (NumberSequenceTable    )



Now we remove the Continues option and create a new customer. We see that less sql statements are executed.



Continues = false, pre allocation = false
First time (7 database calls)
SQL statement: (SysRecordTemplateTable)

SQL statement: (CompanyInfo)

SQL statement: (CustFormletterParameters)

SQL statement: (NumberSequenceReference)

SQL statement: (NumberSequenceTable)

|SQL statement: (NumberSequenceTable)

SQL statement: (NumberSequenceTable)
Second time (2 database calls)
SQL statement: (NumberSequenceTable)

SQL statement: (NumberSequenceTable)








Now we remove the Continues option and allow Pre allocation (caching). We see almost no more sequence related SQL statements:








Continues = false, pre allocation = true
First Time (6 database calls)
SQL statement: (SysRecordTemplateTable)

SQL statement: (CustFormletterParameters)

SQL statement: (NumberSequenceReference)

SQL statement: (NumberSequenceTable)

SQL statement: (NumberSequenceTable)

SQL statement: (NumberSequenceTable)
Second Time (1 database call)
SQL statement: (NumberSequenceTable)






Also removing the format of the sequence will improve the speed. (If you Look at the class NumberSeq::numInsertFormat(), you can see how the filter is used. Because this code uses a lot of loops and string searches, it decrees the speed a lot)




Best practice:


Only use continues number sequences when there is really no alternative. Also inform the customer about the performance impact.


Situations where continues number sequences are often use.


ÿ Documents that leave Axapta. (sales order, purchase orders, etc)
ÿ When the law of the country does not allow interrupts in the voucher series. (When interruption occur, explanation is needed)

Continuous Number Sequences

Continuous number sequences can only be used in transactions (TTSBegin & TTSCommit)

When you use continues number sequences without TTS the following message appear:

System does not support setup 'continuous' of number sequence ‘sequence name’.

This can be solved by un checking continuous or add TTS transactions in the code.
Labels:

Popular posts from this blog

What does this mean: "The form datasource query object does not support changing its AllowCrossCompany property after the form has executed the query."?

I have made a form with datasources vendtable and vendtrans. Inside vendtable_ds.executequery() looks like this: QueryBuildDataSource queryBuildDatasource ,queryBDS_VendTrans_Invoice; ; queryBuildDatasource = this.query().dataSourceTable(tablenum(vendtable)); queryBDS_VendTrans_Invoice = this.query().dataSourceTable(tablenum(vendtrans)); if (curext() == "MASTERCOMP") { this.query().allowCrossCompany(true); } else { this.query().allowCrossCompany(false); } //FilterVendorName = stringedit control on form if (FilterVendorName.text()) { queryBuildDatasource.addRange(fieldNum(VendTable,Name)).value(strfmt("*%1*", FilterVendorName.text())); } else { queryBuildDatasource.clearRange(fieldNum(VendTable,Name)); } //FilterInvoiceNumber = stringedit control on form if (FilterInvoiceNumber.valueStr() == "") { queryBDS_VendTrans_Invoice.enabled(false); } else { queryBDS_VendTrans_Invoice.enabled(true); queryBDS_VendTrans_In...
Read more

Credit Note [Dynamics AX] using X++

This post will help to create credit note for a sales order based on the invent lot id. All the invoices raised for a particular sales line – Lot Id will be raised back as a credit note. Information on Credit Note: A credit note or credit memorandum (memo) is a commercial document issued by a seller to a buyer. The seller usually issues a Credit Memo for the same or lower amount than the invoice, and then repays the money to the buyer or sets it off against a balance due from other transactions Below Code will help to create credit note for all the invoices raised against the sales line -lot id. Please note: This code can be customized as per your requirements. This is just a template to help creating credit note using X++ code. Please test the code before use. static void SR_CreateCreditNote_Sales(Args _args) { // Coded by Sreenath Reddy CustInvoiceTrans custInvoiceTrans; Dialog dialog = new Dialog(“Create credit note – for sales.”); DialogField dfInv...
Read more