New NAV Design Patterns

The NAV Design Patterns Wiki site was announced in November, as a repository containing the first NAV design pattern descriptions, together with a call for contributions.

We would like to say “welcome to the team”, to our new design patterns authors. Their patterns are linked below. If you want to learn from the experience of other Microsoft Dynamics NAV partners and from some of the designs they have implemented or used, then read on.

Posting Routine – Select behaviour

By waldo at ifacto

Meet the Pattern

Send information (parameters) to a processing framework/routine so that it knows what to do, how to behave, .. .

Know the Pattern

For a processing routine to behave correctly, it needs sometimes input of a user to know what it has to do, check or avoid doing.  To do this, usually a piece of UI is getting called (STRMENU) with the question what to do. These input needs to get to the routine.

Continue reading on the NAV Patterns Wiki…

Conditional Cascading Update

by Jan Hoek at IDYN 

Meet the Pattern

The Conditional Cascading Update pattern is used to intelligently populate fields whose values depend on other field values. In this pattern description, the field triggering the update will be called “source field”, and the depending field will be called “target field”. 

Know the Pattern

The value of one table field sometimes depends on the value of another field, typically following an application-defined transformation (note that we’re talking about transformations of field values here. This has nothing to do with e.g. form transformation), such as conversion to uppercase, removal of certain characters etc.

If the target field is non-editable, …

Read more about Conditional Cascading Update on the Wiki…

Setup Specificity Fallback

by Jan Hoek at IDYN 

Meet the Pattern

The Setup Specificity Fallback pattern allows users to efficiently define a potentially complex setup in terms of rules and exceptions to these rules, exceptions to the exceptions, etc.

Know the Pattern

The pattern involves a setup table with a compound (i.e. consisting of more than one field) primary key, where each record in the table maps a combination of primary key values to a particular setup value. However, setting up and maintaining each and every combination could prove to be rather labour-intensive.

Read more on the NAV Design Patterns Wiki…


With best regards from the NAV Design Patterns team.

We're always looking for feedback and would like to hear from you. Please head to the Dynamics 365 Community to start a discussion, ask questions, and tell us what you think!