Deep links available in every form

Ievgen Miroshnikov gave me the idea and Microsoft also has some information here.

The following extends the standard button available in every Dynamics 365 for Finance and Operations form to provide the deep link to the currently select record of the primary form data source.

Copy the link and share it. The recipient will jump directly to the currently selected record.

(I wonder why Microsoft doesn’t provide this in standard D365FO – this is actually what you would expect from the button.)


using Microsoft.Dynamics.AX.Framework.Utilities;
using Microsoft.Dynamics.@Client.ServerForm.Contexts;

/// <summary>
/// The class <c>URLUtility_Extension</c> contains extension methods for the <c>URLUtility</c> class.
/// </summary>
public static class URLUtility_Extension
    public static str generateRecordUrl(str _menuItemName, MenuItemType _menuItemType, DataSourceName _dataSourceName, Map _indexFieldValuesMap, DataAreaId _dataAreaId = curExt())
        System.Uri host                     = SessionContext::Get_Current().Get_RequestUrl();
        UrlHelper.UrlGenerator generator    = new UrlHelper.UrlGenerator();
        generator.MenuItemName              = _menuItemName;
        generator.MenuItemType              = _menuItemType;
        generator.HostUrl                   = host.GetLeftPart(System.UriPartial::Path);
        generator.Company                   = _dataAreaId;
        generator.EncryptRequestQuery       = true;

        if (_dataSourceName && _indexFieldValuesMap)
            MapEnumerator mapEnumerator = _indexFieldValuesMap.getEnumerator();

            var requestQueryParameterCollection = generator.RequestQueryParameterCollection;

            while (mapEnumerator.moveNext())
                requestQueryParameterCollection.UpdateOrAddEntry(_dataSourceName, mapEnumerator.currentKey(), mapEnumerator.currentValue());

        return generator.GenerateFullUrl().AbsoluteUri;

    public static str generateRecordUrlFromDataSource(FormDataSource _formDataSource)
        FormRun         formRun         = _formDataSource.formRun();
        str             menuItemName    = formRun.args().menuItemName();
        MenuItemType    menuItemType    = formRun.args().menuItemType();
        DataSourceName  dataSourceName  =;

        TableId   tableId   = _formDataSource.table();
        DictTable dictTable = new DictTable(tableId);
        DictIndex dictIndex = new DictIndex(tableId, dictTable.primaryIndex());

        int     fieldCount          = dictIndex.numberOfFields();
        Map     indexFieldValuesMap = new Map(Types::String, Types::String);
        Common  record              = _formDataSource.cursor();
        FieldId primaryKeyFieldId;

        for (int fieldIndex = 1; fieldIndex <= fieldCount; fieldIndex++)
            primaryKeyFieldId = dictIndex.field(fieldIndex);

            indexFieldValuesMap.insert(fieldId2Name(tableId, primaryKeyFieldId), any2Str(record.(primaryKeyFieldId)));

        return URLUtility::generateRecordUrl(menuItemName, menuItemType, dataSourceName, indexFieldValuesMap, record.DataAreaId);

    public static str generateUrl(FormRun formRun)
        str url = next generateUrl(formRun);

        if (formRun && formRun.dataSource(1) && formRun.dataSource(1).cursor())
            url = URLUtility::generateRecordUrlFromDataSource(formRun.dataSource(1));
        return url;

Minimal Setup for new Workflow

Sumit created nice overview of workflow-implementations in AX:

Developing a new Workflow

The section below describes briefly, the process of developing a new workflow.

To develop a new workflow, following artifacts or objects need to be created / modified:

  • Workflow Categories
  • Workflow Templates
  • Workflow Query (Document)
  • Workflow Approvals and Tasks (Tasks are optional)
  • Enabling the workflows on the form
  • Workflow submission classes

Let us go through each of these artifacts one by one:

Create Workflow Categories

A workflow category defines the module in which the workflow will be available. Modules are defined by the SysModule enum. You will be doing following here:

  • Create a new category in workflow categories node (AOT>>Workflow>>Workflow Categories)
  • Specify the name and module to which it belongs

Create Workflow Templates (AX 2012: Workflow Types)

A workflow template brings all the different elements of the workflow together. Workflow configurations are created based on a template, and many configurations can be based on the same template. The template defines which actions are allowed and which are required.

You will be doing following here:

  • Create a new template in the workflow templates node (AOT>>Workflow>>Workflow Templates) (AX 2012: AOT>>Workflow>>Workflow Types)
  • Specify a name and category to which it belongs

Next we create a work flow document.

Create Workflow Document

A query defines what tables are used to determine that a workflow can be initiated. Here you will do the following

  • Create a new query (AOT>>Queries)
  • Specify a name and Add required tables to the data source.
  • Create a new class extending from WorkFlowDocument class (AOT>>Classes)
  • Override the method getQueryName and return the name of newly created query
  • Save the class
  • Once query and its supporting class is created, attach this to Workflow template (Specify it under the Document property of template; AX 2012: type)

Next step is to attach Approvals and / or Tasks

Create Workflow Approvals (or Tasks):

An approval route may contain a number of outcomes. It may be approved, rejected, returned or a change may be requested (For task it will be complete, reject or request change). The Workflow Approval element determines which of these outcomes is allowed and what happens in the event of each outcome. Each outcome can trigger specific code by specifying a menu item for each item. Do the following to create an approval

  • Create a new approval object in the Approvals node. (AOT>>Workflow>>Approvals)
  • Specify a unique name for the approval
  • Specify the Document (The class created for query) in the Document property
  • Specify ParticipantProvider. Normally you specify WorkflowUserGroupParticipantProvider, but you can create your own participant provider. (Missing in AX 2012)
  • Specify DueDateProvider. Normally you specify WorkflowWorkCalendarDueDateProvider, but you can create your own due date provider. (Missing in AX 2012)
  • Specify HierarchyProvider. Normally you specify WorkflowLimitHierarchyProvider, but you can create your own hierarchy provider. (Missing in AX 2012)
  • Set the DocumentMenuItem to form menu item where you want the workflow to appear (Example sales order etc.)
  • Approval Outcomes:
    • Use a standard class that acts as an engine for all approval outcomes
    • You are not required to do anything but set the workflow to applicable outcomes, therefore call the same class from different menu items. The menu items simply allow you to use two different labels. In more complex workflows it may be necessary to override or copy and modify this class rather than use it directly. Example: If you have to set an outcome for Approved do the following:
      1. Create a new Action type menu item and specify a name to it
      2. Set ObjectType property to Class and Object property to WorkflowWorkItemActionManager
      3. Now get to Workflow>>Approvals>>Approval_you_created>>Outcomes>>Approve node and specify ActionMenuItem as new menuitem created before.
      4. Repeat Step 2 for all the outcomes you need
    • If you do not need an outcome you can simply disable it by changing Enabled property to No
  • Once completed, drag and drop this approval (or task) into the previously created workflow template (AX 2012: Worfklow Type)

Enable workflow on a form

Now that the workflow template is defined, you can specify which forms will use this template. Do the following:

  • Add a WorkflowState field (More can be added by CreatedBy, Time, Status etc.) to the required table
  • In the desired form, go to the design node properties and set property WorkFlowEnabled to “Yes”, set the WorkFlowDataSource (the table of the previous step) and (AX 2012 only) set the WorkflowType as defined above.
  • If you want, you can override the method canSubmitToWorkflow on the form and specify conditions when user can submit the record to workflow

After enabling the workflow on class, create a class to submit the records to workflow

Create a Submit to Workflow class

To submit a document to workflow, call standard code to prompt the user for a comment and to process the submission. (Look at PurchReqWorkflow class for an example)

  • After creating the submit to workflow class, create a corresponding action menu item
  • Now traverse to the workflow template (AX 2012: Worfklow Type) and specify this submit to workflow class menu item on the SubmitToWorkFlowMenuItem property
  • Once this is done you can then configure the workflow and test it. (You can refer the Workflows – Installation and Configuration document that I sent earlier for configuring the workflows)

This will give you a broad idea as to what needs to be done for creating a workflow.


In AX 2012 it is required to update CIL before the Workflow can be configured.

[updated for AX 2012 on 07/07/2014]

Product configurator data structure

Even though AX 2012 uses the Microsoft Solver Foundation which is not directly accessible to a developer, all data is stored within AX and can be worked with at will. See the follow overview of the data structure:

AX 2012 Product Configurator

Note that most of the data is global, just the PCTemplateComponent table has company specific entries; the table is used for templates – as the name suggests – but also for the item references eg. for Configurator BOM lines.

Edit System Fields

Simple example for creating a record with systems fields set by code:

protected static server CaseLog createCaseLog(RefRecId _caseDatail, CreatedBy _createdBy, CreatedDateTime _createdDateTime)
    CaseLog caseLog;
    if(_createdBy && _caseDatail)
        caseLog.CaseRecId = _caseDatail;
        new OverwriteSystemFieldsPermission().assert();
        caseLog.(fieldNum(CaseLog,CreatedBy)) = _createdBy;
        caseLog.(fieldNum(CaseLog,CreatedDateTime)) = _createdDateTime;
    return caseLog;

Show configuration on hand

The constraint based configuration is saved in relation to the configuration-number (InventDim.ConfigId), however all you see in the On-Hand form is the number.

If you want to see the full configuration that was entered by the user, you can add a simple button to the On-hand form (InventOnhandItem) and override the clicked() method with the following code:

void clicked()
    PCExecuteVariantConfiguration executeVariantConfiguration;
    ProdTable                     tmpProdTable;

    tmpProdTable.InventDimId = InventDim::findOrCreate(inventDim).InventDimId;
    tmpProdTable.ItemId      = InventSum.ItemId;

        executeVariantConfiguration = PCExecuteVariantConfiguration::execute(tmpProdTable, InventSum.ItemId, inventDim.ConfigId);



Open configuration from the on-hand form

Open configuration from the on-hand form

Comparison Framework Sample : BOM Version comparer

I found this blog post Comparison Framework Sample: BOM Version comparer.

Mkz creted a BOM version comparer based on the comparison framework tutorial allowing you to see the line by line differences between BOM versions. I made a quick upgrade to AX 2012 and it now compiles without best practice errors.