Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Implementing Microsoft Dynamics 365 Business Central On-Premise - Fourth Edition

You're reading from  Implementing Microsoft Dynamics 365 Business Central On-Premise - Fourth Edition

Product type Book
Published in Dec 2018
Publisher
ISBN-13 9781789133936
Pages 764 pages
Edition 4th Edition
Languages
Authors (2):
Roberto Stefanetti Roberto Stefanetti
Profile icon Roberto Stefanetti
Alex Chow Alex Chow
Profile icon Alex Chow
View More author details

Table of Contents (22) Chapters

Title Page
Copyright and Credits
Dedication
About Packt
Contributors
Preface
Exploring Dynamics NAV and MSDYN365BC – Overview Microsoft Dynamics NAV 2018 – An Overview General Considerations Implementation Process – Partner's Perspective Implementation Process – Customer's Perspective Migrating Data Upgrading to Dynamics NAV and MSDYN365BC Development Considerations Implementing Functional Changes Data Analysis and Reporting Debugging with Dynamics NAV and MSDYN365BC Popular Reporting Options Microsoft Dynamics 365 Business Central Working and Developing with Docker and Sandboxes Other Books You May Enjoy 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...
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 $15.99/month. Cancel anytime}