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

Creating your first custom action


Custom actions are the most recent addition to server-side extensions. They belong to the family of processes and are similar to custom workflow activities. One advantage of using a custom action, as opposed to a custom workflow activity, is that not only can they be called from a workflow, but they can also be easily called from JavaScript and even be early bound and called as an SDK message call.

In this recipe, we will convert the previously created custom workflow into a custom activity.

Getting ready

You will first need a custom workflow activity to convert into a custom action. The workflow activity created and deployed in the previous two recipes is a good candidate. Similar to previous extensions done from within Dynamics 365, a System Customizer role is required, along with a Dynamics 365 solution to contain your extension. We will reuse the existing Packt solution created in the previous chapters.

How to do it...

  1. In Dynamics 365, navigate to Settings...