Book Image

Microsoft Dynamics 365 Extensions Cookbook

Book Image

Microsoft Dynamics 365 Extensions Cookbook

Overview of this book

Microsoft Dynamics 365 is a powerful tool. It has many unique features that empower organisations to bridge common business challenges and technology pitfalls that would usually hinder the adoption of a CRM solution. This book sets out to enable you to harness the power of Dynamics 365 and cater to your unique circumstances. We start this book with a no-code configuration chapter and explain the schema, fields, and forms modeling techniques. We then move on to server-side and client-side custom code extensions. Next, you will see how best to integrate Dynamics 365 in a DevOps pipeline to package and deploy your extensions to the various SDLC environments. This book also covers modern libraries and integration patterns that can be used with Dynamics 365 (Angular, 3 tiers, and many others). Finally, we end by highlighting some of the powerful extensions available. Throughout we explain a range of design patterns and techniques that can be used to enhance your code quality; the aim is that you will learn to write enterprise-scale quality code.
Table of Contents (19 chapters)
Title Page
Credits
Foreword
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Dynamics 365 applications


Less is more. One of the most powerful UI design principles is to only make available to users the absolute minimum required for them to do their work. French author Antoine de Saint-Exupery summed it up beautifully when he wrote: Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.

Dynamic 365 recently introduced the concept of apps. Apps are nothing but a presentation layer on top of our existing base Dynamics 365 instance. Apps are like a lens that allow a user group to view an instance in a way that makes sense to them. They allow you to simplify the default view into exactly what your user group needs. It is about removing the clutter and the noise that distracts users and affects their experience.

Typically, apps are used when you've got two different business units in an organization that require access to the same data in an instance, but use the data slightly differently. You can design forms and views...