Underneed you find the list of shortcuts I use most in Microsoft Dynamics Ax while developing. General (shortcuts I also use outside AX) CTRL + S : Save. CTRL + C : Copy text to clipboard. CTRL + X : Cut text to clipboard. CTRL + V : Past text from clipboard. CTRL + A : … Continue Reading
Archives
Working with numbersequences – On forms
When you want to implement NumberSequences in a Ax form (new numbersequence when you create a record etc.) you can just implement the ‘numberSeqFormHandler’. Step-by-step:
Working with numbersequences – Keep In Mind
When you are using a Number Sequence, keep in mind that a Continuous Number Sequence is slower than a non-continuous. The reason is that the system creates a record in the table NumberSequenceList (with the status Active) and cleans it up later during TTSCOMMIT. Performance tip: You can improve the performance of a process that creates many … Continue Reading
Working with numbersequences – New Module
In a previous post I explained how to create a new Number Sequence in a existing module (Working with numbersequences – new NumberSequence). In this post I will explain how you can create a new Number Sequence-module. I will create a new module called TEST (lack of inspiration). Step-By-Step:
Placement of code
When you are programming, you have to think about where placing you’re code. Always try to place you’re code nearest to the source so it can be manipulated easily. For instance code that manipulates tables should be placed in that tables methods. Best Practice: Try to minimize the x++ code in forms for the following … Continue Reading
Maximum value RecId
Did you ever wonder what the maximum value of a RecId was? In Ax3.0 it is pritty simple. You know that the RecId was a int value and with the function ‘maxInt()’, you get the value. In Ax4.0 and higher, the RecId is changed from a regular int to in64. There is no such function … Continue Reading
Moving DB-objects to other layers … without losing data
Most of us have already been confronted with the problem of tables being inserted in the wrong layer, and when they already contain data it is very difficult to transfer these objects to the correct layer without losing data. I found the following article on Axaptapedia that helps you with this issue: http://www.axaptapedia.com/Move_DB_objects_to_another_layer
Line Number
When you want to create a table were you want to remain the position of the records you create (like the lineNum field on the SalesLine), you just need to define a field on your new table as a ‘CounterField‘. Step-by-step:
Ax2009 different development licenses
When you want to modify objects in Ax, you have to buy a development license. They are divided in four. Base Package This license gives you access for creating/modifying reports/jobs/queries MorphX This license gives you access tot the Data Dictionary node where tables/Fields/enums/Extended Data Types are maintained. The ability to create forms requires the MorphX … Continue Reading
Lock on form elements in Dynamics Ax
Some end-users like to make their own modifications on their forms (right-click on the form –> setup). Last week I had a customer that was not able to do this trick any more. After some research and a tip from a colleague, I came to the conclusion that this had something to do with overriding … Continue Reading
