Step three – Journals & Entries
by Mark Brummel, Christopher Studebaker, David Studebaker, David Roys, Vjekoslav Ba
Microsoft Dynamics NAV
- Microsoft Dynamics NAV
- Table of Contents
- Microsoft Dynamics NAV
- Microsoft Dynamics NAV
- Credits
- Preface
- 1. Module 1
- 1. Exploring Microsoft Dynamics NAV – An Introduction
- Understanding Microsoft Dynamics NAV
- The functional areas within Dynamics NAV
- History of Dynamics NAV
- Functional areas
- Accessing Dynamics NAV
- Summary
- 2. What's New in NAV 2016?
- Application changes
- Improvements for the application users
- Tablet client
- New application features
- Automatic payment and bank reconciliation
- Signing up for the Bank Data Conversion Service
- Reconciling payments automatically
- Reconciling bank statements automatically
- Social Listening
- Power Business Intelligence
- RapidStart services
- Schedule reports
- E-mailing documents
- Document exchange service (OCR Services)
- Exchange rates update
- Native integration with Dynamics CRM
- Universal app
- Workflow management
- Posting Preview
- Deferrals
- Development changes
- IT changes
- Summary
- Application changes
- 3. Dynamics NAV – General Considerations
- 4. The Implementation Process – From the Reseller
- 5. The Implementation Process on the Customer Side
- 6. Migrating Data
- Tools to migrate data
- RapidStart Services
- Using XMLports to migrate data
- Writing your own tools
- Converting data from the old system to Dynamics NAV's needs
- Master data
- Open entries
- Historical data
- Open documents
- Choosing a go-live date
- Summary
- Tools to migrate data
- 7. Upgrading Microsoft Dynamics NAV
- Upgrading philosophy
- Upgrades prior to Dynamics NAV 2013
- Upgrades from Dynamics NAV 2013 forward
- Upgrading process checklist
- Upgrading steps to NAV 2013
- Upgrading tools
- Summary
- 8. Development Considerations
- 9. Functional Changes on Existing Implementations
- 10. Data Analysis and Reporting
- 11. Debugging
- 12. Popular Reporting Options with Microsoft Dynamics NAV
- 1. Exploring Microsoft Dynamics NAV – An Introduction
- 2. Module 2
- 1. An Introduction to NAV 2015
- NAV 2015 – an ERP system
- Significant changes in NAV 2015
- A developer's overview of NAV 2015
- Hands-on development in NAV 2015
- Summary
- Review questions
- 2. Tables
- An overview of tables
- Enhancing our sample application
- Creating and modifying tables
- Assigning a Table Relation property
- Assigning an InitValue property
- Adding a few activity-tracking tables
- New tables for our WDTU project
- New list pages for our WDTU project
- Keys, SumIndexFields, and table relations in our examples
- Modifying a standard table
- Version list documentation
- Types of tables
- Summary
- Review questions
- 3. Data Types and Fields
- 4. Pages – The Interactive Interface
- Page design and structure overview
- Types of pages
- Page Designer
- Page components
- WDTU Page Enhancement – part 1
- Page controls
- WDTU Page Enhancement – part 2
- Page Actions
- Learning more
- Summary
- Review questions
- 5. Queries and Reports
- Queries
- Reports
- Report components – overview
- Report data flow
- Report components – detail
- Creating a Report in NAV 2015
- Summary
- Review questions
- 6. Introduction to C/SIDE and C/AL
- 7. Intermediate C/AL
- 8. Advanced NAV Development Tools
- NAV process flow
- Role Center pages
- XMLports
- Web services
- Summary
- Review questions
- 9. Successful Conclusions
- Creating new C/AL routines
- Multi-language system
- Multi-currency system
- Navigate
- Debugging in NAV 2015
- C/SIDE Test-driven development
- Other Interfaces
- NAV Application Server (NAS)
- Client Add-ins
- Customizing Help
- NAV development projects – general guidance
- Design for efficiency
- Updating and upgrading
- Supporting material
- Summary
- Review questions
- 1. An Introduction to NAV 2015
- 3. Module 3
- 1. Introducing Dynamics NAV Patterns and Software Architecture
- What do we mean by 'patterns'?
- Microsoft Dynamics NAV Design Patterns
- Patterns elements and hierarchy
- Building blocks
- Metadata
- Base application
- Summary
- 2. Architectural Patterns
- 3. Design Patterns
- 4. Building an Example Application Using Patterns
- 5. Coding Best Practices
- 6. Anti-patterns and Handling Legacy Code
- 7. Building Solutions Using Patterns
- 1. Introducing Dynamics NAV Patterns and Software Architecture
- Bibliography
- Index
Now that we have Master Data, we can start recording transactions that are linked to the master data. We will implement this using an Example Journal and Example Entries. The Entries will be linked to both the Example Person and the Example Product table.
When creating a Journal we need a set of Tables, Pages, Codeunits and Reports. There are quite a few Journals in Microsoft Dynamics NAV with different levels of complexity, but they all have the same basic structure.
Creating a brand new Journal is not easily documented step-by-step, and would cost a considerable page count in this book. For most architects, creating a new journal is not a frequent task. Even in the standard Dynamics NAV application, new journals are added only in every few big releases.
When creating a new Journal in Dynamics NAV there is a trick that you can use, but it requires basic knowledge of the syntax that is used for external object text files.
In Microsoft Dynamics NAV the Resource Journal & Entry structure is very isolated and close to the Pattern definition that we use. We can mark the following objects in the object designer as illustrated in the next screenshot, and export them as a text file:
Using any text editor, we can then use the Find and Replace to create our own journal and entry using the following steps:
- Create a new object number structure for your add-on and replace the numbers. Remember to do this in an intelligent way, as the number you are replacing might be used for other purposes than object numbering:
- Find and Replace the object names with your names. The Resource Journal uses the
ResourceandResnames. In our Journal we will useExampleandEx. - Change Table Relations to your tables.
- Replace the Text Constants in the
ResJnlManagementCodeunit:
After importing your text file you can fine-tune your journal. In our example journal we have removed the recurring option to simplify the process.
The Resource Journal also uses the Test Report-Print
Codeunit 228. This Codeunit needs to be modified to support the Example Journal. - After importing the text file and cleaning it up, we should have the following objects:
Although many Journal Line tables in Dynamics NAV contain C/AL code in the OnValidate triggers of the table, this code is only intended to be used when the table is used from the user interface as a journal.
An example of OnValidate code in the General Journal Line is displayed in the following screenshot:
Journals are also used during the posting of Documents and other processes in NAV. During these processes the Journal Line table acts as an Argument table as illustrated in the following screenshot of Codeunit Sales-Post (80):
During these processes, the data is already validated during the entering of the Document and tested in the Test Near and Test Far parts of the posting routine.
-
No Comment