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

Using Flow to move data between CDS and Dynamics 365


Now that we have created a feedback entity in our Common Data Services and have a PowerApp application that populates data into our entity, we will need a mechanism to transport the data from one platform to the other. Flow will help us replicate that data.

In this recipe, we will automate the creation of a new feedback record in Dynamics 365 when a feedback record is created in CDS.

Getting ready

Given that we're moving feedback data from one CDS to Dynamics 365, we will need the feedback entity created in both platforms. The Dynamics 365 entity does not have to exactly match the CDS one; however, some degree of attribute compatibility is required. For example, the sentiment can be a picklist in the CDS, but in Dynamics 365, it may be a text field.

In addition to the platform's schema, you will need the correct license to be able to create and use a Flow process. Flow can be purchased independently or bundled with Dynamics 365 Plan 1 or higher...