Microsoft Dynamics NAV - C/SIDE Solution Development -

Microsoft Dynamics NAV – C/SIDE Solution Development

Locus IT ServicesMicrosoft Dynamics NAV – C/SIDE Solution Development

Lesson 2: Seminar Feature Integration

Seminar Feature Integration

Seminar Feature Integration : You are now ready to integrate the Seminar Management features with the standard application and to one another. You have already integrated some features earlier, such as linking lists to card pages, or enabling users to call posting routines from document pages. Except for these simple and most common feature integration steps, you must provide deeper integration to maintain a consistent user experience across the application.

Integrating these features enables users to be more productive for the following reasons:

  • It reduces the number of clicks for users to access related features that are available in all relevant pages.
  • It reduces time that you spend on data entry and filtering by defaulting master data and document number fields.
  • It reduces errors that are created by typing incorrect information by defaulting field values.

Solution Design

CRONUS International Ltd. provided no specific functional requirements about the feature integration. Most of the work that relates to feature integration belongs to the domain of Microsoft Dynamics NAV 2013 standards and best practices.

However, the following two nonfunctional requirements address customer productivity and ease-of-use issues:

  • The solution must be consistent, user-friendly, and easy to learn and to use.
  • Any custom-built functionality must follow the standards, principles, and best practices of Microsoft Dynamics NAV 2013, and must seamlessly integrate into the standard application. The solution must enable users to be productive and spend as little time as possible searching and filtering.

You can address these requirements by integrating features. Microsoft Dynamics NAV 2013 standard functionality provides many examples of integrating features when you develop your custom application functionality.

The three most common user tasks in Microsoft Dynamics NAV 2013 are as follows:

  • Creating new transactions
  • Maintaining and processing existing transactions
  • Analyzing transaction history

The most common user task is entering transactional information. This includes documents and journals. Because documents and journals are always related to a master record, the majority of master pages in Microsoft Dynamics NAV 2013 provide a quick way to enter a document or a journal for a master record. For example, you can create a new quote or an invoice for a customer directly from the Customer Card or Customer List, or you can access the Item Journal directly from the Item Card or Item List.

In addition to creating new documents for a master record, you must quickly access any existing documents that are related to that master record. For example, from Customer Card or Customer List, you can quickly access any quotes, invoices, or other document types that are related to the selected customer. This provides an intuitive user experience, and makes it easy for users to quickly access related information.

Finally, users typically access transaction history for a master record. Therefore, users can click Ledger Entries on each master record card. This provides a standard and consistent way to access the ledger entries for the master record. Ledger Entries are a mandatory action on every master page. You can also press CTRL+F7. This is the system-wide shortcut for accessing related ledger entries from any master page. For example, to access Customer Ledger Entries from Customer Card, you can press CTRL+F7, or click Ledger Entries.

Locus IT Project Management Office
What’s it?