Book Image

Dynamics 365 Application Development

By : Deepesh Somani, Nishant Rana
Book Image

Dynamics 365 Application Development

By: Deepesh Somani, Nishant Rana

Overview of this book

Microsoft Dynamics 365 CRM is the most trusted name in enterprise-level customer relationship management. The latest version of Dynamics CRM comes with the important addition of exciting features guaranteed to make your life easier. It comes straight off the shelf with a whole new frontier of updated business rules, process enhancements, SDK methods, and other enhancements. This book will introduce you to the components of the new designer tools, such as SiteMap, App Module, and Visual Designer for Business Processes. Going deeper, this book teaches you how to develop custom SaaS applications leveraging the features of PowerApps available in Dynamics 365. Further, you will learn how to automate business processes using Microsoft Flow, and then we explore Web API, the most important platform update in Dynamics 365 CRM. Here, you'll also learn how to implement Web API in custom applications. You will learn how to write an Azure-aware plugin to design and integrate cloud-aware solutions. The book concludes with configuring services using newly released features such as Editable grids, Data Export Service, LinkedIn Integration, Relationship Insights, and Live Assist
Table of Contents (20 chapters)
Title Page
Copyright and Credits
Dedication
Packt Upsell
Contributors
Preface
Index

Dynamics 365 Workflow versus Microsoft Flow


There are certain scenarios which can be implemented using either Dynamics Workflow or Microsoft Flow. Following are a few points we can consider when deciding.

If a scenario can be implemented within Dynamics 365 using Workflow, then Workflow is the better choice. This is because we can easily manage and monitor it from within CRM, through System Jobs. For managing and monitoring a flow, we need to go outside CRM and do the same from within Flow's portal.

Workflow can run both synchronously and asynchronously. Workflow will trigger immediately when conditions are met. So, in scenarios where we want immediate action to be taken, Workflow is a better choice. Moreover, Workflow is solution-aware, so it can move easily from one environment to another.

Microsoft Flow is a better fit in scenarios where we want to seamlessly integrate with third-party applications and services such as Twitter, Facebook, Yammer, and so on. To implement this within Workflow...