Form Transformation Objectives

Microsoft Dynamics Nav 2009

Form Transformation enables you to:

  • Transform forms to pages (basic transformation)

  • Tailor resulting pages for the RoleTailored client (UX transformation)

Form-to-page transformation is a basic transformation process that takes form objects from the Microsoft Dynamics NAV Classic application and creates page objects that you can use in the RoleTailored client.

User experience (UX) transformation supplements basic form-to-page transformation by adding additional user interface elements to pages that take advantage of the new user experience in the RoleTailored client.

Basic Transformation

Basic transformation is the conversion of a form, including its existing functionality and business logic, to a new page by mapping the form essentials—properties, controls and code—to the corresponding page components.

The mapping logic is based on rules that are generically applied to all forms. This mapping logic enables you to automate the transformation process. The transformation tool includes built-in mapping rules. In addition to the built-in mapping rules, the transformation input files to the tool include modifiable rules. For more information about the transformation tool and the mapping rules, see Form Transformation Tool Overview.

In addition to replacing existing elements on a form with the corresponding new elements on a page, mapping logic also extends to and includes rules that do the following:

  • Ignore   The transformation tool ignores an existing element on a form without replacing it with a corresponding new element on a page. Typically, this occurs in one of the following cases:

    • The RoleTailored client supports the equivalent behavior in a different way than the Classic client.

    • The logic does not require input from the original form.

    • There is not an equivalent element on a page in the RoleTailored client.

  • Add a property   The transformation tool adds properties to a page that were not on the original form. For example, PageType is a new page property that is a prerequisite to render a page. CardFormID is another new page property. You must assign a CardFormID to a list form that you will transform to a page. Other properties added to a page through transformation are a part of UX transformation.

The following tables list examples of generic rules that the transformation tool applies automatically during a basic transformation.

Form control Mapping rule Page control



Grid (Repeater)





In most cases, the CaptionML value of the label is transformed to the CaptionML of the parent or adjacent control. For more information, see Control Mapping Rules.

Caption of field control is used as label.



MatrixBox control is not available.

Form Property Mapping Rule Page Property



None. Pages and controls have built-in rendering and resizing logic.



None. Pages and controls have built-in rendering and resizing logic.



None. Pages and controls have built-in rendering and resizing logic.












Not supported



Not supported


Add new



Add new


Code on a Form Mapping Rule Code on a Page

Formatting code


Replaced with dynamic properties: Editable, Enabled, Visible, and Indentation.

Functionality code - triggers

Replace unsupported triggers by moving code to supported triggers

Supported triggers.

Functionality code - methods

Ignore unsupported methods


For complete mapping rules, see Form Transformation Reference.

UX Transformation

Through the UX transformation, the automatically generated pages can be tailored to make use of new user interface features in the RoleTailored client. You can either tailor pages through the transformation process or directly in the page object. For more information about the different transformation methods, see Form Transformation Methods. This section describes tailoring pages as part of the transformation process. For more information about designing pages, see Creating and Maintaining Pages.

You can enhance a page as part of a UX transformation in the following ways:

  • Adding FactBoxes and reports to pages.

  • Adding new actions that do not exist on the form.

  • Promoting frequently used actions and reports onto the Action Pane.

  • Assigning icons to actions.

  • Promoting fields to Fast Tab headers.

  • Adding home parts to a role center.

  • Modifying shortcut keys.

For more information about UX transformation, see Specifying Form Transformation Rules with the Transformation Input Files Editor.

The following diagrams illustrate how a form looks before transformation and how the corresponding page looks after transformation.

Sales Order form in Classic client Sales Order page in RoleTailored client

The following changes were made to the sales order task page during UX transformation:

  • Three FactBoxes were added to the right side of the page: Customer Sales History, Sales Line Details, and Notes.

  • Frequently used actions, such as Post, Post and Print, and Release have been added to the Action Pane with the appropriate icons.

  • The Lines FastTab has been placed directly under the General FastTab.

  • Selected fields, such as Customer Bill-to No., Payment Terms Code, and Due Date have been marked with Essential importance so that they appear as a summary on the collapsed Invoicing FastTab.

Unlike basic transformation, UX transformation requires specific instructions for each form. You define these instructions in the transformation input files. For more information about transformation input files, see Understanding Form Transformation Input Files.

Community Additions