Export (0) Print
Expand All

Preparing for Form Transformation by Redesigning Forms

Microsoft Dynamics Nav 2009

You may need to redesign some of your forms to make them preserve the business logic and layout when you transform the form to a page. Redesigning means that you have to either create a new form to replace the one that cannot be transformed, or modify the original form. Usually you only need to redesign a few forms in your application.

Why Redesign Your Forms?

The following reasons may be why you may need to redesign some of your existing forms:

  • Unsupported controls

  • Matrix-like layouts do not transform successfully

  • New user experience (UX) guidelines

Unsupported Controls

The RoleTailored client does not support certain control types that are used in the Classic client. The unsupported controls are the following:

  • MatrixBox

  • Shape

You cannot map these controls in the Classic client to controls in the RoleTailored client. If a form contains one of these types of controls, then it will not transform. Matrix forms are examples of forms that use these types of controls. You must start at the beginning and design a new form.

Matrix-Like Layout

Certain controls, when used together, create a matrix-like layout. Although the individual controls are supported, the matrix-like layout will not transform successfully. You must redesign forms with a matrix-like layout.

New UX Guidelines

The RoleTailored client has new navigation principles and UX guidelines. This means that you must modify the behavior of some Classic client forms before they can be transformed, for example:

  • In the RoleTailored client, the user must always be able to move from a list place to a card.

  • In the RoleTailored client, Journal forms must connect to their respective batch lists

  • In the RoleTailored client, separate list forms must be created for each document type.

Some forms in the standard application were redesigned to new forms for UX improvements. The following table shows these forms.

Original form Redesigned form Description of change

Form 6512, Item Tracking Code Card

Form 9368, _Item Tracking Code Card

All check boxes are in one column.

Form 402, Sales Order Statistics

Form 9402, _Sales Order Statistics

The tables at the bottom of each tab were removed.

Form 403, Purchase Order Statistics

Form 9403, _Purchase Order Statistics

The tables at the bottom of each tab were removed.

Form 5914, Service Order Statistics

Form 9404, _Service Order Statistics

The tables at the bottom of each tab were removed.

Form 7002, Sales Prices

Form 9420, _Sales Prices

The Currency Code Filter drop-down list is moved to the General tab so that there is only one tab on the form instead of two.

Form 7004, Sales Line Discounts

9421, _Sales Line Discounts

The Currency Code Filter drop-down list is moved to the General tab so that there is only one tab on the form instead of two.

Several advanced confirmation forms in the standard application were redesigned so that they transform to pages successfully. The following table shows these forms.

Form ID Form name

342

Check Availability

343

Check Credit Limit

476

Copy Tax Setup

511

Change Exchange Rate

579

Post Application

591

Payment Tolerance Warning

692

Import Style Sheet

695

Confirm Financial Void

722

BA Password Entry

802

Online Map Address Selector

5135

Customer Link

5136

Vendor Link

5137

Bank Account Link

5142

Save Segment Criteria

5526

Make Supply Orders

5985

Service Item Replacement

6002

Cancelled Allocation Reasons

6022

Reallocation Entry Reasons

6024

Reallocation Entry Reasons

6079

Contract Amount Distribution

6513

Enter Quantity to Create

6515

Enter Customized SN

8622

Company Setup

99000833

Check Prod. Order Status

99000882

Change Status on Prod. Order

99000884

Create Order From Sales

99000901

Check Date Conflict

Redesigned Forms in Microsoft Dynamics NAV 2009

Several forms in the Microsoft Dynamics NAV 2009 standard application have been redesigned. The following topics list the redesigned forms in the standard application:

The following topics describe how to redesign the various types of forms that cannot be successfully transformed:

You can use the information in these topics in the following ways:

  • If your forms have the same pattern as the forms in these topics, redesign your forms in the same manner.

  • If your forms do not have the same pattern as the forms in these topics, use the changes that are described to offer insight into alternative redesign solutions for your specific forms.

Community Additions

ADD
Show:
© 2014 Microsoft