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: Prerequisite Knowledge for Dimensions
Prerequisite Knowledge for Dimensions : A dimension is additional information that is attached to records, primarily for analysis. Table fields are static, unchangeable attributes of records and are predetermined by the developer. Whereas, dimensions are dynamic, configurable attributes that the user selects and sets up.
A company’s accounts consist of many entries from many sources. Accounts are associated with many activities within the company. It is frequently necessary to create statements, statistics, and analyses that are extracts of the complete financial statements. These extracts can be created by using individual dimensions or combinations of dimensions.
If you set up a dimension called Department, and then use this dimension and a dimension value when you post an entry, you can retrieve information later, such as items that were sold and the departments that sold them. If more than one dimension was used on posted entries, the user can create a richer analysis of a company’s activities. For example, a single sales entry can include multiple dimension information about the account to which the item sale was posted, where the item was sold, who sold it, and the type of customer who made the purchase.Microsoft Dynamics NAV
By using dimensions, you can analyze trends and compare various characteristics across a range of entries. The analysis view functionality is especially effective for this purpose. However, you can also use filters, account schedules, and reports to create informative dimensions analyses.
You can also use dimensions to support business rules by influencing how a user can combine dimensions and how dimensions can be posted. This may be useful if certain departments cannot use particular accounts or sell to particular customers.
- Master records
- Document headers and lines
- Posted document headers and lines
- Journal lines
- Ledger entries
Each dimension can have an unlimited number of dimension values. For example, a dimension called Department can have dimension values of Sales, Administration, and so on. Dimensions can also be hierarchical with multiple levels of values organized in parent/child relationships. Dimensions can also include totaling groups that have headers and footers.