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: Seminar Management Department Page
Seminar Management Department Page
Seminar Management Department Page : Provide a Role Center for users to work with a new application area as a way to increase user productivity. However, the Role Center alone is not the only task that is available to improve the user experience with the Microsoft Dynamics NAV 2013 client for Windows.
Many users do not belong to the seminar manager role, and use different Role Centers than the Seminar Manager Role Center. For example, accountants generally use the general ledger functionality, and accounts payable employees usually access the purchases and payables application area. However, these users may require occasional access to seminar-related information that their role centers do not provide.
To give all users access to the SeminarManagement application area, you must define the SeminarManagement department page. By providing this page, you make sure that every user can access the Seminar Management functionality in Departments, and that all objects that are related to Seminar Management can be accessed by using the Search field.
Similar to Role Center functionality, CRONUS International Ltd. functional requirements do not explicitly mention departments. However, the following nonfunctional requirement applies: 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.
If you do not provide a department page for SeminarManagement, your solution does not meet the goals of this requirement. Therefore, you must develop a new MenuSuite object that contains the menu definition for the SeminarManagement department page.
Your goal is to develop the Seminar Management department page that integrates in the Departments page in Microsoft Dynamics NAV 2013. To do this, you must develop the new SeminarManagement menu in a new company-level MenuSuite. The “Seminar Management Department Page” image shows the SeminarManagement Department page in the Microsoft Dynamics NAV 2013 client for Windows.