- Microsoft Dynamics NAV 2013 Application Design
- Table of Contents
- Microsoft Dynamics NAV 2013 Application Design
- Credits
- Foreword
- About the Author
- Acknowledgments
- About the Reviewers
- www.PacktPub.com
- Preface
- 1. Introduction to Microsoft Dynamics NAV
- Versions and history
- What is this book about
- Setup versus customization
- The beauty of simplicity
- Design patterns
- Structure of this book
- The Role Tailored concept
- The building blocks
- Dynamics NAV in throughout supply chain
- Some basic design patterns
- Architectural design patterns
- Balancing
- Flow fields and flow filters
- More journals and entries
- Combining the journals into processes
- Other patterns
- Summary
- 2. A Sample Application
- 3. Financial Management
- 4. Relationship Management
- How companies work
- Customizing relationship management
- Summary
- 5. Production
- What is production?
- Basic production principles
- Getting started
- Assembling
- Design patterns
- The items
- Item costing
- Item tracking
- The bill of materials
- Calculating the standard cost
- Creating the inventory
- Adjusting cost item entries
- Posting inventory cost to G/L
- Check, check, and double check
- Recalculating the standard unit cost
- Assembly orders
- Check costing (again)
- Recalculating the unit cost (again)
- Standard cost worksheet
- Item Revaluation Journal
- The result
- Summarizing item costing in 10 steps
- Manufacturing
- Specialized production
- Assembling
- Vertical industry implementation
- Summary
- 6. Trade
- The process
- Sales and purchasing
- Inventory management
- Warehouse management
- Reservations
- Trade in vertical industries
- Summary
- 7. Storage and Logistics
- 8. Consulting
- 9. Interfacing
- Interface types
- Interfacing technologies
- Standard application interfaces
- Interface methodologies
- Interfacing into the future
- Summary
- 10. Application Design
- Application life cycle
- Design to use
- Design to Maintain
- Design to support
- Design to upgrade
- Design to perform
- Design to analyze
- Version and object management
- Development methodology
- The project
- Summary
- Application life cycle
- A. Installation Guide
- Index
When customizing Microsoft Dynamics NAV, you can use proven concepts in the application. These proven concepts are called design patterns. There are three types of design patterns.
Architectural patterns are the main data processes and table structures. Examples are master data, singleton tables, documents, and posting and archiving processes.
Although this is the name that people use for the entire concept, design patterns are reusable elements to solve specific problems, such as number series and blocked entity.
Different development techniques are called implementation patterns. Examples are proxy, façade, temporary datasets, and hooks.
Application programming interfaces (APIs) are reusable blocks of code that generally do not change. They are as important to know to work with Dynamics NAV as .NET libraries are to work in C#. Within Microsoft Dynamics NAV, we have several building blocks that are reused but not changed. Examples are address formatting and the navigate page.
-
No Comment