Dynamics 365 FO / AX - thoughts on application development and customizations

A colleague of mine needed to determine (runtime) what ax-tier his code was running on. We digged around, and he came up with the solution: if (isRunningOnServer()) { // Server } else { // Client } As a footnote he needed this check to make some code to refresh the AOS-code cache, when implementing quick-fixes to an environment running with multiple AOS-instances.

I've been assigned a task where the merge between VAR and CUS-layer of the application is necessary. I like to make my self a TO-do-list of elements to be processed, so I can check an item when it is done. I wrote a small job to identify elements in the application that were represented in both VAR and CUS-layers thus representing a potential layer-conflict. The job produces an info-log with the potential conflicts that can be copied in to Excel to be used as a TO-DO-list. static void JSOVarVapAndCusConflictsJob9(Args _args) { UtilIdElements utilIdElements; UtilIdElements VarVapUtilIdElements; Map elemMap; MapIterator elemMI; UtilElementType recType; RecId utilId; int pos; str 60 elementName; elemMap = new Map(Types::String,Types::String); while select UtilIdElements where (utilIdElements.utilLevel == UtilEntryLevel::cus) && UtilIdElements.parentId == 0 { ...

Recently I've had an assignment where we needed to "split up" a label file. The assignment was to: * read thorugh a label file. * If any labels were encountered with a number bigger then N these should be written to a new label file AND any references to these labels should be replaced in the code. So I exported all adjustments/code made to an .xpo file, and I took a copy of the label file. Then I wrote a class that did the "splitting up" of the label file and the search/replace of labels in the code (.xpo file). This made for use of an other entry in this blog, namely extracting text from a label, and for some interesting use of the TextBuffer object for search/replace. Here you can download the code. Use at own risk !!!

Put the following code in the GLOBAL class in a new method called setFormModal : static void setFormModal(int _thisHWND, boolean _bModal) {     DLL _winApiDLL;     DLLFunction _EnabledWindow;     DLLFunction _getTop;     DLLFunction _getNext;     DLLFunction _getParent;     void local_enableWHND(int _lHWND)     {         int lnextWnd;         lnextWnd = _getTop.call(_getParent.call(_lHWND));         while (lnextWnd)         {             if (lnextWnd != _lHWND)                 enabledWindow.call(lnextWnd, (!_bModal));       ...

Useful debugging tip for tracking down the point where an exception is thrown. Some times it can be difficult to determine where an exception is thrown. Is it e.g. the validatefield method on a data source field on a form that throws the exception, or is it the validatewrite method on the data source or even the validatewrite method on the table it self. A useful trick to establish the point in the code where the exception is thrown, is to set a break point in line 11 in the method add in the class Info. You can find the Info class at the bottom at the class subtree in the AOT. This will stop execution and activate the debugger each time something is added to the infolog which is normally done when an exception is thrown.

How to create, compile and run code at RUNTIME. In some situations the need for making "generic" code arises. This is a little example that generates, compiles and runs code to delete the contents of table PBACustGroup. The code is made as a job, but transforming this code into a method on a class, and calling this method with parameters that allows it to identify the table, suddenly makes us able to delete several selected tables with very little code. It also allows for USER CONTROLLED actions, for example letting the user build a liste of tables he would like to delete, and then calling the code for each of these tables. static void TestGenericCode(Args _args) {     XppCompiler XppCompiler;     str code;     str tableName = "PBACustGroup"; // Here we define the name of the table ;     // A compile object is created     XppCompiler = new XppCompiler();     // Here th...

How to extract label text. This code shows how to get the text of a specific label for a specific module, for a specific language. This might come in handy when constructing a text to be printed on a report, that will more than one label text. // This code allows you to extract the label text of a specific label, for a specific module, // for a specific language // // Handy when constructing text fields containing many values and labels for printing // // str = labeltxt("gls",element.design().languageId(),200); str labeltxt(str _labelModule,LanguageId _languageId, LabelIdNum _labelNo) {     Label l;     l = new label(_languageId);     return l.extractString(l.name(_labelModule,_labelNo)); }