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 3: Navigate Integration
Navigate Integration : The Navigate feature lets users view a summary of the number and type of entries with the same document number or posting date. This feature is very useful for finding the ledger entries or other types of posted information that result from certain transactions. The Navigate feature is one of the central traceability features in Microsoft Dynamics NAV 2013, and one of its most versatile features.
When users post a transaction, they rely on the Navigate feature when they must trace the results of the transaction. Users access the Navigate feature from any page that displays any type of posted entries or documents. The Navigate feature displays every resulting entry.
This makes it important to fully integrate any custom functionality that includes a posting process with the Navigate feature. Integrating the Navigate feature improves the traceability of your own transactions and the resulting posted documents and ledger entries.
Navigate Feature Architecture
The architecture of this feature is simple, even though the Navigate feature performs the complex task of searching and then displaying database records to the user in the appropriate page. When you search, the Navigate feature takes advantage of simple filtering mechanisms. When it shows pages, it uses the default lookup forms.The Navigate feature is completely contained within the page 344, Navigate. The “Navigate Page (344)” figure shows the Navigate page.
The most common way to use the Navigate page is to specify the Document
No., Posting Date or both, and then click Find. The field controls for the
Document No. and Posting Date filters are bound to the DocNoFilter and PostingDateFilter variables. When the user clicks Find, it calls the FindPush function.C/Side Solution development.
The power of the Navigate feature is not only its capability to search for records in the database, but its ability to show the relevant page for each record type that it finds. The ShowRecords function controls that part of the functionality.
Users can call the ShowRecords function by either clicking Show, or drilling down any of the rows that represent the found record types.
The ShowRecords function is large, however, it follows the same simple pattern to display records. This pattern consists of one large CASE block. Based on the table ID of the selected row, the default lookup page runs over the same table that was filtered earlier in the FindRecords or FindExtRecords function. The user can quickly access the details of any posted transaction by knowing only its posting date or document number.