Book Image

Implementing Microsoft Dynamics 365 Business Central On-Premise - Fourth Edition

By : Roberto Stefanetti, Alex Chow
Book Image

Implementing Microsoft Dynamics 365 Business Central On-Premise - Fourth Edition

By: Roberto Stefanetti, Alex Chow

Overview of this book

Microsoft Dynamics Business Central is a full business solution suite and a complete ERP solution, which contains a robust set of development tools; these tools can help you to gain control over your business and can simplify supply chains, manufacturing, and operations. Implementing Microsoft Dynamics 365 Business Central On-Premise covers the latest features of Dynamics Business Central and NAV from the end users' and developers' perspectives. It also provides an insight into different tools available for implementation, whether it's a new installation or migrating from the previous version of Dynamics NAV. This book will take you from an introduction to Dynamics NAV 2018 through to exploring all the techniques related to implementation and migration. You will also learn to expand functionalities within your existing Microsoft Dynamics NAV installation, perform data analysis, and implement free third-party add-ons to your existing installation. As you progress through the book, you will learn to work with third-party add-on tools. In the concluding chapters, you will explore Dynamics 365 Business Central, the new Cloud solution based on the Microsoft NAV platform, and techniques for using Docker and Sandbox to develop applications. By the end of the book, you will have gained a deep understanding of the key components for successful Dynamics NAV implementation for an organization.
Table of Contents (22 chapters)
Title Page
Copyright and Credits
Dedication
About Packt
Contributors
Preface
Index

Define acceptable gaps and workarounds


The standard product is a great product, but obviously it cannot contain all the functionalities necessary for the company. It is necessary to try to adapt to it or use workarounds to manage what may seem unmanageable.

In addition to the work of consultants, already seen in the previous chapter, the customer must play their part in trying to adapt as much as possible to the standard and accept any unmanageable gaps that can be bypassed by workarounds proposed by the consultant. The customer (the key user of the process in general) must always be the sponsor of the project and of the product.

If, instead, new gaps/requirements emerge that cannot be managed through workarounds (during the project or after the go-live date), it is necessary to classify them so as not to alter the course of the project, under an example of classification. For example, we can classify the new requirements/gaps that are detected in this way:

  • Need to start
  • Need after starting
  • Nice...