TIP: Pay attention when use caching display methods on forms

A tipical performance tip is to put all display methods on datasource cache:
https://msdn.microsoft.com/en-us/library/aa596691.aspx

Using something like that on init method of datasource
this.cacheAddMethod(tableMethodStr(CustTable, Name));

Pay attention, the value of all cached methods is set when data is fetched from the back-end database. If you put a display method on a separated tab, not vibile when the form is opened, the method is called the same for each record of datasource when form start, causing a performance problem if the display method is complex. If you remove the method from the cache the display method is called only when the control appears to the user.

Than, add the method cache only if the control is visibile to the user into the main grid or main tab, otherelse assessed whether the performances have a real advantage.

INFO: Dynamics AX 2009 file extensions

I found good information which I want to share with all of you, some times we wonder as to what a particular ax system file is and what it does now you can bank upon the list given below for all such enigma. Dynamics AX uses a lot of file extensions, but luckily, there is a logic to them, so you can easily identify their purpose.Most of these files are located in the application folder (AX 2009):

C:\Program Files\Microsoft Dynamics AX\50\Application\Appl\[your_application]

The extensions have 3 characters:

• The first character indicates the owner of the file:

• a: application

• k: kernel

• The second character indicates the content of the file:

• l: label

• o: object

• t: text

• d: developer documentation

• h: help

• Third character indicates the type of file

• d: data

• i: index

• c: cache

• t: temporary

Using this logic, we can easily name all file extensions, and understand their purpose.

In the application folder:

• ALD extension: Application Label Data files These files contain the labels and label comments for a specific language of a label file.

• ALC extension: Application Label Cache files These files contain the application label cache. These files can be deleted when the AOS is stopped.

• ALI extension: Application Label Index files The .ali files contain an index to the .ald files. These files can be deleted when the AOS is stopped.

• ALT extension: Application Label Temporary files. These files contain new labels before they are committed to the .ald file.

• AOI extension: Application Object Index file. The AOI file contains an index to the AOD files. You can delete this file when the AOS is stopped. Be sure to delete this when you have copied layers from one AX installation to an other.

• ADD extension: Application Developer Documentation Data files. These files contain the documentation that is found under the Application Developer Documentation node. These files are localized, just like label files.

• ADI extension: Application Developer Documentation Index files. This is the index to the ADD file.

• AHD extension: Application Help Data files. The AHD file contains the documentation aimed at the end user. In the AOT, this is found in the “Application Documentation” node.

• AHI extension: Application Help Index files. This is the index to the AHD file.

• AOD extension: Application Object Data file. This is the ‘AX layer file’, each of these files represents one layer.

• KHD extension: Kernel Help Documentation files. These files contain the kernel help documentation you can find in the AOT in the tree node System Documentation.

• KHI extension: Kernel Help Index files. The KHI file is the index to the Kernel Help file. Located in Server/bin:

• KTD extension: Kernel Text Data file. This file contains system text strings. These are used in the interface of AX and for system messages.

• KTI extension: Kernel Text Index file. This is the index to the KTD file.

Client side (not following the naming logic):

• AUC extension: Application Unicode Object Cache file (as from AX 4.0). This file is created on the client side, and is used to improve performance by caching AX objects. When you are in the situation where an AX client keeps using ‘old code’, or where something works on one client and not on the other, removing the AUC file might be the solution. You can find this file in the directory "C:\Documents and Settings\[USERNAME]\Local Settings\Application Data for xp, or C:\Users\USERNAME\AppData\Local for vista.

• AOC extension: Axapta Object Cache file (Untill Axapta 3). This is the ‘old’ version of the AUC file but serves the same purpose.

* Note: GREEN file's can be deleted when AOS is stopped

HOWTO: Debug the AifOutboundProcessingService

If you need to go more in depth using debugging of an outbound you have to write down a couple of customization on standard code:

• Comment out the runas method on AifOutboundProcessingService.runAsUserInPartition method and replace with a direct call to processAsUser method. 

/*

// runAs currentUser and process all messages in the container.

new RunAsPermission(runAsUserId).assert();

// BP deviation documented

runas(runAsUserId,

classnum(AifOutboundProcessingService),

staticmethodstr(AifOutboundProcessingService, processAsUser),

messageIdContainer,

runAsCompany,

'',

runAsPartition);

// Revert the permission

CodeAccessPermission::revertAssert();

*/

AifOutboundProcessingService::processAsUser(messageIdContainer);

Important: You have to run the code on the same company and partition specified on runAsCompany and runAsPartition parameter.

• Comment out or o skip execution this line of code on AifDispatcher.dispatchOperation method

//new AifDispatcherPermission().demand();

For process the message queue use the new AifOutboundProcessingService().run() method

HOWTO: Create computed columns in Views on Dynamics AX 2012

Reposted from http://daxture.blogspot.it/2015/03/computed-columns-in-views-dynamics-ax.html

Computed columns have been using in SQL server since many versions but this feature was available Dynamics AX since version 2012.
Follow steps described here to learn how to create view and walthrough the complete example to understand how can we add computed columns in AX 2012 Views. More examples can be found from here; http://daxmusings.codecrib.com/2011/10/computed-view-columns-in-ax-2012.html 

Well, here is an example which illustrates how can we add computed columns in a view with different logic.

Computed column; Returning Field in View

public static server str compAmount()
{
   #define.CompView(SWProjForecastCost)
   #define.CompDS(ProjForecastCost)
   #define.CostPrice(CostPrice)


   return SysComputedColumn::returnField(tableStr(#CompView), identifierStr(#CompDS), fieldStr(#CompDS, #CostPrice));
} 

Computed column; Converting UTC Date to Date in View

public static server str compDate()
{
   #define.CompView(SWProjForecastCost)
   #define.CompDS(ProjForecastCost)
   #define.ActualDateTime(ActualDateTime)


   str sDateTime;

   sDateTime = SysComputedColumn::returnField(tableStr(#CompView), identifierStr(#CompDS), fieldStr(#CompDS, #ActualDateTime));

   return SysComputedColumn::fromUtcDateToDate(sDateTime);
} 




Computed column; Returning Enum Value in View

public static server str compGeneralTransType()
{
   return SysComputedColumn::returnLiteral(Transaction::ProjectInvoice);
}

Computed column; Multiplying two coulmns and returning resultant from View

private static server str compTotalCostPrice()
{
   #define.CompView(SWProjForecastCost)
   #define.CompDS(ProjForecastCost)
   #define.QtyCol(Qty)
   #define.PriceCol(CostPrice)


   return SysComputedColumn::multiply(
           SysComputedColumn::returnField(
               tableStr(#CompView),
               identifierStr(#CompDS),
               fieldStr(#CompDS, #PriceCol)
           ),
           SysComputedColumn::returnField(
               tableStr(#CompView),
               identifierStr(#CompDS),
               fieldStr(#CompDS, #QtyCol)
           )
         );
}

Computed column; Case Statement in View

public static server str TransType()
{
   #define.CompDS(ProjForecastCost)
   #define.CompView(SWProjForecastCost)
   str ret;

   str ModelId = SysComputedColumn::returnField(identifierStr(SWProjForecastCost), identifierStr(ProjForecastCost), identifierStr(ModelId));
   ret = "case " + modelId +
         " when 'Sales' then 'Forecast Sales' " +
         " when 'Orders' then 'Forecast Orders' " +
         " when 'Latest' then 'Forecast Latest' " +
         " end";
   return ret;


}

Case Statement for this view looks like in SQL server as below;

   CASE T2.MODELID

      WHEN 'Sales' THEN 'Forecast Sales'

      WHEN 'Orders' THEN 'Forecast Orders'

      WHEN 'Latest' THEN 'Forecast Latest' END

DLP: New training material on the DLP – Get ready for the upcoming Dynamics releases

Many new DLP resources:

http://community.dynamics.com/nav/b/365talentportalnav/archive/2015/11/27/new-training-material-on-the-dlp-get-ready-for-the-upcoming-dynamics-releases

X++: How to find what projects an object from the AOT exists in (Recursive)

To find out what projects an AOT object exists in, use this script.
It's recursive, than it can find methods or inner nodes too

ProjectNode projectNode;
ProjectListNode projectListNode;

TreeNode treeNode;
TreeNodeIterator treeNodeIterator;

// Object we are searching for
TreeNode tnSearch = TreeNode::findNode(@'\Classes\MHT_DOCF_MasterTable');

void find(TreeNodeIterator _innerTreeNodeIterator)
{
TreeNode innerTreeNode;
;
innerTreeNode = _innerTreeNodeIterator.next();
while (innerTreeNode)
{
if (innerTreeNode.treeNodePath() == tnSearch.treeNodePath())
info(strfmt("Found in shared project %1", treeNode.AOTname()));
find(innerTreeNode.AOTiterator());
innerTreeNode = _innerTreeNodeIterator.next();
}
}

;

projectListNode = SysTreeNode::getSharedProject();
treeNodeIterator = projectListNode.AOTiterator();

treeNode = treeNodeIterator.next();
while (treeNode)
{
projectNode = treeNode;
projectNode = projectNode.loadForInspection();
find(projectNode.AOTiterator());
treeNode = treeNodeIterator.next();
}

TIP: Error executing code: The field with ID '0' does not exist in table 'SysExtensionSerializerExtensionMap'.

If you ever get "Error executing code: The field with ID '0' does not exist in table 'SysExtensionSerializerExtensionMap'." error in CIL, it may happen it is the table extension framework + the standard buf2buf function to blame.

Somehow, if you pass a Map instead of a table to buf2buf function, the following line fails:

_to.(fieldId) = _from.(fieldId);
However, if you replace this line with:

fieldName = fieldId2name(_from.TableId, fieldId);
 _to.setFieldValue(fieldName, _from.getFieldValue(fieldName));

everything is fine both in X++ and in CIL.

P.S. I didn't dare to change the standard buf2buf method. Istead, I created another method and used it in the table extension framework logic, which failed because of the issue (\Data Dictionary\Maps\SysExtensionSerializerMap\Methods\copyExtensionTableData)


Reposted: https://community.dynamics.com/ax/b/dynamicsaxnotesonthecuffs/archive/2016/04/04/error-executing-code-the-field-with-id-39-0-39-does-not-exist-in-table-39-sysextensionserializerextensionmap-39