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

Dynamics Axapta: Sales Orders & Business Connector

Well, again folllowing my same idea of writting close to nothing and pasting code, I'll paste in some code to create a sales order from some basic data and the invoice it. I'll try to explain more in the future. AxaptaObject axSalesTable = ax.CreateAxaptaObject("AxSalesTable"); AxaptaRecord rcInventDim = ax.CreateAxaptaRecord("InventDim"); AxaptaRecord rcCustTable = ax.CreateAxaptaRecord("CustTable"); rcCustTable.ExecuteStmt("select * from %1 where %1.AccountNum == '" + MySalesOrderObject.CustAccount + "'"); if (MySalesOrderObject.CurrencyCode.Trim().Length == 0) MySalesOrderObject.CurrencyCode = rcCustTable.get_Field("Currency").ToString().Trim(); string sTaxGroup = rcCustTable.get_Field("taxgroup").ToString().Trim(); //set header level fields axSalesTable.Call("parmSalesName", MySalesOrderObject.SalesName.Trim()); axSalesTable.Call("parmCustAccount", M
Read more

Passing values between form and class

Class name is EmplDuplication and Form is EmplTable . void clicked() {    MenuFunction mf;    args args = new Args();    ;     args.record(EmplTable);     mf = new menufunction(identifierstr(EmplDuplication), MenuItemType::Action); mf.run(args); } Meanwhile, in the main() method of the EmplDuplication class, we need to put this Axapta x++ code to get the datasource: static void main(Args args) {     EmplDuplication EmplDuplication; EmplTable localEmplTable; ;     if(args.record().TableId == tablenum(EmplTable)) localEmplTable = args.record();     ... }
Read more