Learn Dynamics 365 Finance and Operations(Axapta)

We have gone through the number sequence issue that we are facing in Axapta. Below are my findings on the issue, Please suggest how to proceed on this issue. Continuous:- Select this check box for a continuous sequence.(if this is selected system will generate continues number sequence, which is selected in our Case) Cleanup - When this option is selected, the number sequence is cleaned up automatically.(this option is selected in Our case) This option is automatically selected when the number sequence is continuous (it is ticked in our case), and should not be cleared. For continuous number sequences, the next available number from the sequence is used when a transaction is entered. If a number is generated but the transaction fails, automatic cleanup allows the number to be used again. You can set up a time interval for automatic cleanup in the Interval field. (In Our case Time Interval is set to 24 hours which according to Microsoft is a Best Practice) Root C

Include a try catch around all transactions that could result in deadlock. Make sure the try for a deadlock is idempotent meaning no matter how many times the try is attempted, it will yield the same result. Consider the clarity when deciding the number of return statements in a method. Use throw instead of ttsAbort. Avoid display methods where possible. Set Optimistic Concurrency Control (OccEnabled) to Yes for most tables. Do not include user interaction inside a database transaction. Keep database transactions as short as possible. Run code on the Application Object Server (AOS) whenever possible. Use where clauses in select statements and in queries that align with indexes. If method calls are used to test conditions, put the method calls after the other conditions. If the other conditions fail, then you will not incur the cost of running the method. Minimize the size of database transactions. Consider specifying a field list in

We have found that in a number of AOS crash cases they are resolved by installing the latest kernel hotfix. Therefore it is recommended that you consider implementing the latest kernel rollup as part of your maintenance. This could mean applying the latest kernel rollup once a quarter. Since the kernel hotfixes are cumulative, easy to uninstall, and do not include X++ fixes they are typically able to be installed with a lot less effort than an application hotfix. We do recommend that you apply the kernel rollup in a non-production environment and do some testing before applying it in your production environment. Please see the information from the  AX Kernel Patching  section on how to update to the latest kernel hotfix rollup. If you implement code when users are in the system you could have cache or data access issues that result in an AOS crash. Therefore, when implementing code in your production environm