Becoming a Dynamics 365 Finance and Supply Chain Solution Architect: Implement industry-grade finance and supply chain solutions for successful enterprise resource planning (ERP)

This book provides in-depth insights and trusted techniques for aspiring Dynamics 365 Finance and Supply Chain Solution Architects. A valuable resource

This book is OK given its enormous scope and that it's a first edition. It is not comprehensive, nor is it uniquely insightful. But it does cover the basics, and I would hope to see a second edition add to and update the rapidly changing materials. I would also hope to see this book pivot now that the FastTrack team itself has published a comprehensive 780 page D365 Implementation Guide. It's no longer necessary to cover methodology. Instead, perhaps cover insights and experiential aspects. There's a two star review here that is overly harsh. Great job Brent contributing to the D365 community and knowledge base. Keep it up!!!

As a consultant and architect I found this book extremely helpful and clarified a lot of questions I had from an architectural point of view. The book is very well put together and helped me identify areas needed for the architectural configuration.

This book serves as a good Introduction for those wanting to become architects already in the ecosystem as well as those switching into the Dynamics 365 world from other platforms. It really does well in laying out Microsoft's vision and direction for the product and how one can adopt their best practices to ensure a successful implementation.

This book is clear, concise, and offers a straightforward approach to becoming a D365FO Solution Architect. There are a lot of things to consider when becoming a Solution Architect, and Brent has covered a majority of them, providing real world examples and use cases as well. I enjoyed reading through his experiences and his knowledge of the system along with those experiences made for a very interesting read! If you are considering becoming a Solution Architect, then this book is a must read!

Dawson’s book Becoming a Dynamics 365 Finance and Supply Chain Solution Architect is a comprehensive guide for anyone interested in the role of a Solution Architect. He covers the entire project lifecycle, from initiation to closure, and shares valuable insights from his own experience. He illustrates the best practices and common mistakes of ERP implementation with real-world examples. This book is a good read for anyone who wants to learn more about implementing Microsoft Dynamics 365 Finance and Supply Chain and how to work effectively with the implementation teams. It will also help you understand the rationale behind the decisions and actions involved in the process and ultimately, help you make better decisions during the implementation.

This is a well written book with enough detail to give you an insight into the spectrum of activities a Dynamics 365 F&SCM solution architect would be involved in. There's plenty of useful information, written in a friendly and informative tone, with real world examples woven through the text to provide practice to the theory. As it is introductory level book, there's sometimes a lack of depth on the many subjects in covers - but this is to be expected with such a wide subject, and the balance is about right for the intended audience.

Book is easy to understand for someone new to this role or wanting to move to SA role. Book provides basics to start with and explains the day in a life of an SA.

Thank you for taking the time to identify the important aspects of the F&O implementation. A must read for anyone on an F&O project.

I began reading from License Chapter as it was my most immediate pain, however, the book does nothing to simplify the intricate licensing structure if Microsoft and my confusions remained the same before and after studying the chapter very carefully. Rest of the chapters are okay, but knowledge is surface level at best. The printing company must have assumed the book is to be read by some aliens whose eyes zoom in 2x to a normal human eye. Font couldn't have been possibly smaller (the irony is that there is a lot of white space on the page margins). Even if the material would have been good enough, it is impossible to read it at a stretch for more than two minutes without causing a major strain to your eyes.

I was hoping this book would be more useful than it turned out to be. The chapter listing looked fairly comprehensive, but the content therein was often quite weak. The data migration section in particular was very weak, and I felt skipped most of the important aspects. It also had some some rather unusal statements such as: 'The only data that needs to be migrated is “non-transactional” data'. Really? and BYOD as a solution? I'd like to see that get past the finance and external audit functions. The back up diagrams would make Noddy happy, although big ears might have something to say about it. It became clear to me at least that the example implementations discussed were of limited complexity. The cutover section I skimmed as I found the range of items I would expect to be covered, having recently implemented a large scale international ERP, was possibly useful at best as a heads up for someone with no prior experience in these kind of activities, but anyone who has been through hardcore cutovers would point out some of the glaring mistakes and omissions. Weak at best. The biscuit was well and truly taken when I read: 'In my experience, I’ve had PMs whose knowledge was limited, but they thought it was part of their job to help solution the project. I want the PM to keep track of time, make sure tasks are completed, and make sure we’re well within the budget. As the SA, I don’t tell them how to manage the project, and I don’t want them to create the solution. My experience as a former lead architect for many years for a large well respected international consultancy with hands on experience is that an enthusiastic and encouraged Project Manager is worth their weight in gold and are able to contribute in ways that can be well received by a team. Maybe the author would like the project manager to limit their role to make the tea and provide biscuits for team meetings as well? The irony of talking about the importance of the team was not lost on me. After reading that statement, which in my opinion came across as smug and arrogant, I decided that I had had enough of reading this self-congratulatory, smug, book and I decided to not waste any more of my time.