Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Programming Microsoft Dynamics 365 Business Central

You're reading from   Programming Microsoft Dynamics 365 Business Central Build customized business applications with the latest tools in Dynamics 365 Business Central

Arrow left icon
Product type Paperback
Published in Apr 2019
Publisher Packt
ISBN-13 9781789137798
Length 536 pages
Edition 6th Edition
Arrow right icon
Authors (3):
Arrow left icon
Christopher D. Studebaker Christopher D. Studebaker
Author Profile Icon Christopher D. Studebaker
Christopher D. Studebaker
David Studebaker David Studebaker
Author Profile Icon David Studebaker
David Studebaker
Marije Brummel Marije Brummel
Author Profile Icon Marije Brummel
Marije Brummel
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

Preface 1. Introduction to Business Central FREE CHAPTER 2. Tables 3. Data Types and Fields 4. Pages - The Interactive Interface 5. Queries and Reports 6. Introduction to AL 7. Intermediate AL 8. Advanced AL Development Tools 9. Successful Conclusions 10. Assessments 11. Other Books You May Enjoy

Report naming

Simple reports are often named the same as the table with which they are primarily associated, plus a word or two describing the basic purpose of the report. Common key report purpose names include the words Journal, Register, List, Test, and Statistics. Some examples include General Journal - Test, G/L Register, and Customer - Order Detail.

When there are conflicts between naming based on the associated tables and naming based on the use of the data, the usage context should take precedence in naming reports, just as it does with pages. One absolute requirement for names is that they must be unique; no duplicate names are allowed for a single object type. Remember, the caption (what shows on the printed report heading) is not the same as the name (the internal name of the report object). Each one is a different report property.

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime