Book Image

Implementing Microsoft Dynamics 365 Customer Engagement

By : Mahender Pal
Book Image

Implementing Microsoft Dynamics 365 Customer Engagement

By: Mahender Pal

Overview of this book

Microsoft Dynamics 365 for Customer Engagement (CE) is one of the leading customer relationship management (CRM) solutions that help companies to effectively communicate with their customers and allows them to transform their marketing strategies. Complete with detailed explanations of the essential concepts and practical examples, this book will guide you through the entire life cycle of implementing Dynamics 365 CE for your organization or clients, and will help you avoid common pitfalls while increasing efficiency at every stage of the project. Starting with the foundational concepts, the book will gradually introduce you to Microsoft Dynamics 365 features, plans, and products. You’ll learn various implementation strategies and requirement gathering techniques, and then design the application architecture by converting your requirements into technical and functional designs. As you advance, you’ll learn how to configure your CRM system to meet your organizational needs, customize Dynamics 365 CE, and extend its capabilities by writing client-side and server-side code. Finally, you’ll integrate Dynamics 365 CE with other applications and explore its business intelligence capabilities. By the end of this Microsoft Dynamics 365 book, you’ll have gained an in-depth understanding of all the key components necessary for successful Dynamics 365 CE implementation.
Table of Contents (14 chapters)

Deploying Dynamics 365 CE solutions

After completing Dynamics 365 CE development and testing, it's time to deploy our changes to the production environment. In Chapter 6, Customizing Dynamics 365 CE, we discussed Dynamics 365 CE solutions that we can use to deploy our changes to other environments. We also discussed the points that can help us to select a managed or unmanaged solution. Depending on the type of deployment, we do what we need to in order to plan it accordingly. For example, if we are moving some updates to production, we can do it after working hours, but if we are going to roll out a complete application, it will require a good amount of downtime. Most of the time, these types of rollouts are done on weekends. If we are doing an upgrade, solution deployment may or may not impact the business—for example, if we are doing a side-by-side upgrade where...