Book Image

Programming Microsoft Dynamics NAV 2013 - Third Edition

Book Image

Programming Microsoft Dynamics NAV 2013 - Third Edition

Overview of this book

Microsoft Dynamics NAV 2013 is a complete and robust ERP system that is accompanied by a comprehensive set of development tools. You will learn how to master these tools and tailor Microsoft Dynamics NAV 2013 to meet your customer's specific business needs."Programming Microsoft Dynamics® NAV 2013" will lead you from start to finish, teaching you how to use this incredible ERP software whilst simultaneously making you a more productive developer. You'll learn how to implement your solutions, as well as evaluating, managing and appraising Dynamics NAV 2013 productions and projects.You will be empowered with the skills and knowledge that you need to get the job done and exceed your client's expectations. Step by step, you will learn how to use NAV, master the C/AL programming language, as well as the construction and uses of each object type. Ultimately, you will be able to bring your NAV 2013 solution together with fantastic efficiency.Hands-on development examples and additional material teach you by example and uncover the insider knowledge that only years of experience can provide, truly unleashing your productivity and potential.
Table of Contents (19 chapters)
Programming Microsoft Dynamics NAV 2013
Credits
Foreword
About the Authors
Acknowledgements
About the Reviewers
www.PacktPub.com
Preface
Index

Page Components


All pages are made up of certain common components. The basic elements of a page object are the page triggers, page properties, controls, control triggers, and control properties.

Page Triggers

The following screenshot shows the page triggers. The Help section Page and Action Triggers provide good general guidance to the event which causes each page trigger to fire. Note that the OnQueryClosePage trigger isn't related to any Query object action.

In general, according to best practices, we should minimize the C/AL code placed in Page triggers, putting it in a Table or Field trigger or calling a Codeunit function instead. However, many standard pages include a modest amount of code supporting page specific filter or display functions. When we develop a new page, it's always a good idea to look for similar pages in the standard product and be guided by how that page operates internally. Sometimes special display requirements result in complex code being required within a page...