Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Implementing Microsoft Dynamics 365 Business Central On-Premise

You're reading from   Implementing Microsoft Dynamics 365 Business Central On-Premise Explore the capabilities of Dynamics NAV 2018 and Dynamics 365 Business Central and implement them efficiently

Arrow left icon
Product type Paperback
Published in Dec 2018
Publisher
ISBN-13 9781789133936
Length 764 pages
Edition 4th Edition
Arrow right icon
Authors (2):
Arrow left icon
Roberto Stefanetti Roberto Stefanetti
Author Profile Icon Roberto Stefanetti
Roberto Stefanetti
Alex Chow Alex Chow
Author Profile Icon Alex Chow
Alex Chow
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Exploring Dynamics NAV and MSDYN365BC – Overview FREE CHAPTER 2. Microsoft Dynamics NAV 2018 – An Overview 3. General Considerations 4. Implementation Process – Partner's Perspective 5. Implementation Process – Customer's Perspective 6. Migrating Data 7. Upgrading to Dynamics NAV and MSDYN365BC 8. Development Considerations 9. Implementing Functional Changes 10. Data Analysis and Reporting 11. Debugging with Dynamics NAV and MSDYN365BC 12. Popular Reporting Options 13. Microsoft Dynamics 365 Business Central 14. Working and Developing with Docker and Sandboxes 15. Other Books You May Enjoy

Data model principles


After analyzing the standard functionality, if there are needs to do custom development, it is important to develop the solution with the same structure that Microsoft Dynamics NAV and Microsoft Dynamics 365 Business Central on-premise use in their modules (it's necessary to follow the standard of product).

Note

For Microsoft Dynamics 365 Business Central, SaaS is different because it is not possible to access the source code and it is possible to develop customizations only through extensions; this will be discussed in the following paragraphs.

The users that are going to use the functionalities are users that are also going to use the standard parts of the application. To avoid confusing them, it is essential to use the same philosophy and the same structure everywhere. This way, once a user knows one part of the application, they can intuitively use the other modules.

This is something that will also help us; we do not have to reinvent the wheel every time. There is...

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
Banner background image