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

A few key points about business rules


The following are important points regarding business rules that we need to consider before we decide on using them:

  • We cannot use the business rule to hide tabs and sections of a form.
  • The OnChange event of the field will not be triggered if that field's value is set using a business rule.
  • There is a limitation of 10 if...else conditions in a business rule.
  • The business rule will not run if it references a field that is not in the form. It will not show any error message.
  • The business rule, if not defined with Scope as Entity, will run only during the load of the form and when the value of a field changes. It will not run on save of the form.
  • Business rules run in order of their activation. So, if we have multiple interrelated business rules defined for an Entity, the business rule that was activated first will run first followed by the other business rule in order of their activation.
  • If we have both JavaScript and business rules defined for a specific field...