Module 1: DATA AND PROCESS MODEL
Module 2: MASTER TABLES AND PAGES
Module 3: DOCUMENTS
Module 4: POSTING
Module 5: FEATURE INTEGRATION
Module 6: REPORTING
Module 7: STATISTICS
Module 8: DIMENSIONS
Module 9: ROLE TAILORING
Module 10: INTERFACES
Module 11: WEB SERVICES
Module 12: TESTING AND DEBUGGING
Module 13: SQL SERVER OPTIMIZATION
- Lesson 1: SQL Server for Microsoft Dynamics NAV
- Lesson 2: Representation of NAV Tables and Indexes in SQL Server
- Lesson 3: Collation Options
- Lesson 4: SQL Server Query Optimizer
- Lesson 5: SQL Server Query Optimizer
- Lesson 6: Data Access Redesign
- Lesson 7: C/AL Database Functions and Performance on SQL Server
- Lesson 8: Bulk Inserts
- Lesson 9: Locking, Blocking, and Deadlocks
- Lesson 10: SIFT Data Storage in SQL Server
- Lesson 11: SQL Server Profiler
Lesson 2: Integrating Seminar Management with Dimensions
Integrating Seminar Management with Dimensions
Integrating Seminar Management with Dimensions : In Microsoft Dynamics NAV 2013, dimensions serve two purposes: they enable the expansion of the existing data model with additional attributes that meet a company’s business need for simple multi-dimensional analysis of data; and they support simple data-driven business rules that relate to data validity during posting.
When you extend the application by using new application areas or functionality such as master records, documents, or journals, you should take advantage of the standard dimension management functionality to give users a consistent user experience. You have already developed many features for the new Seminar Management application area. You now must integrate the dimension management features with Seminar Management functionality.
The CRONUS International Ltd. functional requirements do not include specific details about dimensions. The legacy application that they used prior to the implementation of Microsoft Dynamics NAV 2013 has no similar functionality, and CRONUS International Ltd. is unfamiliar with the concept of dimensions.
However, two of the following functional requirements for CRONUS International Ltd. can apply to dimensions:
- The solution must use the standard functionality of Microsoft Dynamics NAV 2013 wherever possible. The solution must not duplicate functions that are already present in the application or cause redundant functionality.
- The solution must be consistent, user-friendly, 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.
To provide a consistent user experience and to integrate with dimension management features of standard Microsoft Dynamics NAV 2013, you must change many of the objects that you have previously developed, including tables, pages, and codeunits. You must extend both your data model to integrate with the standard dimension model, and your application features to integrate with the standard dimension process model, as explained in the Prerequisite Knowledge lesson.