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
Prerequisite Knowledge : Before developing the solution for handling seminar registrations, you must become familiar with several more development concepts in Microsoft Dynamics NAV 2013.
Working with Objects as Text Files
Microsoft Dynamics NAV 2013 Development Environment lets you import and export objects to move them between different environments. For example, you can export objects from your development environment, and then import them into the test environment or the production environment
Developers frequently import and export objects as text files, because it provides the following benefits:
- You can easily analyze the contents of the objects before you import them.
- You can change the contents of the objects outside Microsoft Dynamics NAV 2013 Development Environment.
- Microsoft Dynamics NAV 2013 does not let you import the objects if you do not have an appropriate license. This reduces risks of accidental or unintentional replacement of objects in a production environment.
The resulting text file contains all details of the object. The first line for every object in the file begins with the word OBJECT, the object type, number, and name. The text for the rest of the object follows.
Multilanguage Functionality in Text Messages
When you create messages for the user, you must make sure that the text and the object names in the messages are enabled for multilanguage functionality.
If your code has to display any errors, confirmations, or messages, do not enter those text messages directly in the C/AL code. This makes your code dependent on the language that you used initially. Any users who run Microsoft Dynamics NAV 2013 in another language may be unable to understand the messages.Microsoft Dynamics NAV 2013 does not recommend hardcoding text messages directly in the C/AL code because it ignores multilanguage functionality. It degrades the user experience by enabling your code to correctly run only under a single user interface language. In the earlier example, the captions of tables and fields were hardcoded. If these captions and fields were changed, the resulting text message could be confusing for users