New Application Design Patterns: Totals and Discounts on Subpages

To increase discoverability and productivity, critical information, such as statistics, can be moved from separate pages onto the document where it is needed. For example, documents should clearly display totals and discounts information to provide quick overview, make it easy to relate the amounts to the document currency, and to allow the user to see and apply discounts directly on the document.


Before Microsoft Dynamics NAV 2015, totals and discount information was scattered between the document and the Statistics page, which made it less discover-able and less usable for new users. It was difficult to see the discount amounts, relate the amounts to the currency of the invoice, and it was not-intuitive that you had to update the Statistics page to see updates on the document. In addition, the result of the update was not visible on the main document, which added to the confusion.

Totals and discount information logically belongs on the document, as is the case in many competitor products.

The Statistics page contains too much information for most common scenarios, and only a part of the information is visible on the related document. See the following example for sales order statistics.

With the pattern implemented, selected statistics fields are placed on the sales order, as in the following example.

This new layout gives precise and complete information about totals and discounts, with discounts on the left side and totals on the right side. The currency is clearly shown, and the layout resembles a printed document. The values are always updated (with some exceptions that are explained in the next following sections), and the user can apply a discount directly on the document.

Read more on the NAV Design Patterns wiki...

By Nikola Kukrika at Microsoft Development Center Copenhagen

Comments (5)

  1. Jeremy says:

    One of the problems is that the totals on pages like the Sales Order are love/hate.   Customers LOVE to see the totals info right there – but they hate the room it takes.  Unlike other parts, you cannot collapse the area with a FastTab control.  One of the most commonly requested customs from our new 2015 users (both from new implementations and upgrades) is a check box toggle that shows/hides this group.

  2. Allan says:

    I second that!

  3. guido robben says:

    I think it's more usefull to put this in a factbox.

  4. Jens Glathe says:

    Vertical screen space goes at a premium these days. Wasting it with ribbons, toolbars, grpup bars, unchangeable static fields is a bad idea. BTW: Is there a property to force the state of groups? Like, expanded, closed?

  5. Tim says:

    I agree, a factbox would be better, the real estate left for the lines is simply not adequate.  I would have trouble selling this to the customer moving from classic design.

Skip to main content