Search icon
Subscription
0
Cart icon
Close icon
You have no products in your basket yet
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Becoming a Dynamics 365 Finance and Supply Chain Solution Architect

You're reading from  Becoming a Dynamics 365 Finance and Supply Chain Solution Architect

Product type Book
Published in Jun 2023
Publisher Packt
ISBN-13 9781804611494
Pages 270 pages
Edition 1st Edition
Languages
Author (1):
Brent Dawson Brent Dawson
Profile icon Brent Dawson

Table of Contents (18) Chapters

Preface 1. Part 1: Architectural Considerations and Best Practices for D365 Finance and SCM
2. Chapter 1: Overcoming Challenges in D365 Finance and SCM Projects 3. Chapter 2: Understanding the Microsoft FastTrack© Process 4. Chapter 3: Dealing with Integrations 5. Chapter 4: Efficient Security Design 6. Chapter 5: Planning for Successful Data Migration 7. Chapter 6: Licensing Challenges 8. Part 2: From Solution Design to Deployment – Practical Advice
9. Chapter 7: How to Plan a D365 F&SCM Project 10. Chapter 8: Learning the Client’s Business 11. Chapter 9: Collecting Project Requirements 12. Chapter 10: ALM Tools and Applications 13. Chapter 11: Human Change Management 14. Chapter 12: Building a Blueprint Solution 15. Chapter 13: Deploying the Project Solution 16. Index 17. Other Books You May Enjoy

Why do integrations fail?

As mentioned previously, integrations are one of the areas that can cause an SA grief during a project. There are several different issues that may cause the failure of a D365 integration. Listed here are the top 5 issues.

Working in silos

Unfortunately, many companies fall into this situation. They have separated out the way their company works so that it’s easier to manage internally. This prevents the business units and IT from working together to take full advantage of how the integration will work. This happens mostly because neither side fully understands what the other side does and how they interact with the different systems that will utilize integration.

Data dependency

The single biggest reason to use integration is so we can transmit data between systems. When we’re creating sales orders for customers, we need to have the following in the system:

  • Information on products
  • The total amount of product inventory...
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 €14.99/month. Cancel anytime}