Search icon CANCEL
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
Implementing Microsoft Dynamics 365 for Finance and Operations Apps

You're reading from   Implementing Microsoft Dynamics 365 for Finance and Operations Apps Learn best practices, architecture, tools, techniques, and more

Arrow left icon
Product type Paperback
Published in Mar 2020
Publisher Packt
ISBN-13 9781789950847
Length 528 pages
Edition 2nd Edition
Arrow right icon
Authors (4):
Arrow left icon
JJ Yadav JJ Yadav
Author Profile Icon JJ Yadav
JJ Yadav
Rahul Mohta Rahul Mohta
Author Profile Icon Rahul Mohta
Rahul Mohta
Yogesh Kasat Yogesh Kasat
Author Profile Icon Yogesh Kasat
Yogesh Kasat
Sandeep Shukla Sandeep Shukla
Author Profile Icon Sandeep Shukla
Sandeep Shukla
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Introduction to Dynamics 365 Finance and Operations 2. Methodology and Initiation FREE CHAPTER 3. Lifecycle Services (LCS) and Tools 4. Architecture, Deployment, and Environments 5. Requirements and Process Analysis 6. Configuration and Data Management 7. Solution Planning and Design 8. Integration Technologies, Planning, and Design 9. Customization and Extension 10. Analytics, Business Intelligence, and Reporting 11. Testing and Training 12. Managing Go-Live and Post Go-Live 13. One Version Service Updates 14. Other Books You May Enjoy

Best practices and recommendations

Here are a few considerations to keep in mind while designing your integration solution for Dynamics 365 for Finance and Operations:

  • Simplify the overall architecture and try to reduce the number of integrations between applications wherever possible. It is one of the areas that causes recurring issues in production.
  • Clearly define the master system for each data element, even though you may have it stored in multiple places. In some cases, this may have to be defined at the field level. For example, a customer master is stored in CRM and Finance and Operations as well. CRM might be the master for all the customer information except the credit limit.
  • Ideally, you should avoid duplicating data across multiple systems, although in some cases you cannot avoid it for business reasons or for systems to work. For example, customer records are required...
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 €18.99/month. Cancel anytime