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 1: Table Types and Characteristics
Table Types and Characteristics
Table Types and Characteristics : As a business management application, Microsoft Dynamics NAV manages and processes lots of data. All data is stored in tables. From a technical perspective, all tables are the same, as they all contain fields, keys, and triggers. From a functional perspective, there are different types of tables that serve different purposes.
Understanding different table types in Microsoft Dynamics NAV enables you to efficiently customize existing functionality and design new application areas.
A master table contains information about the subject of its application area. For example, the Customer table is a master table. This is the subject of the sales, marketing, and receivables application areas. A master table is somewhat static. Users regularly enter new master records, but rarely change existing master records.
All transactional tables in an application area are related to a master table. The master table itself is related to many other (usually supplemental) tables. There is at least one ledger table that is related to a master table. Master tables frequently contain many FlowFilters and FlowFields, most of which relate to its corresponding ledger tables. Most application areas have only one master table, although some master tables are shared between different application areas, and some application areas occasionally have more master tables.
Naming Master Tables
The name of a master table relates to the names of the records in the table. For example, the Customer table is named Customer because each record within it contains information about a customer.
Primary Key and Other Standard Fields
The primary key of a master table is named No., is of type Code, and of length 20. The value of this field is assigned automatically through the number series functionality.
The description field of a master table is named Name or Description, is of type Text, and is 50 characters long. This field, together with the No. field, is always included in the DataCaptionFields property of the table, so that these fields are displayed in the title bar of the table pages.
Many master tables contain a field named Blocked. This is typically of type Boolean. This field indicates whether users can use a master record in transactions. Instead of deleting a master record that is no longer used, users can mark it as Blocked. This makes sure that an attempt by any user or system action to use that master record fails. Sometimes this field is of type Option. This prevents the use of the master record in some specific transactions, but allows for use in others. For example, in Customer and Vendor tables, this field is of type option, and allows for several levels of blocking a customer or a vendor.