As we began to settle into 2019, we finally saw a cohesive and logical strategy emerge concerning Microsoft Dynamics 365 Customer Engagement (formerly known as Dynamics CRM). The announcement of the Microsoft Power Platform helped in setting a positive direction of travel for the various so-called “business application” products – namely, the Common Data Service, PowerApps and Microsoft Flow….
Continue Reading The CRM Chap’s Article on their blog
Summarising the New Dynamics 365 Customer Engagement API Request Limits & Allocations
As we began to settle into 2019, we finally saw a cohesive and logical strategy emerge concerning Microsoft Dynamics 365 Customer Engagement (formerly known as Dynamics CRM). The announcement of the Microsoft Power Platform helped in setting a positive direction of travel for the various so-called “business application” products – namely, the Common Data Service, PowerApps and Microsoft Flow.
Blog Syndicated with The CRM Chap’s Permission
More About This Author
Array
Dyn365CE29 August 2021Migrating Microsoft Dataverse Access Team Templates via Azure DevOps- Dyn365CE22 August 2021Returning All Form Controls via JavaScript (Model-Driven Power App)
- Dyn365CE15 August 2021Exam PL-600 Revision Notes: Evaluating an Organisation, Metrics and Existing Systems
- Dyn365CE8 August 2021Exam PL-600 Revision Notes: Initiating Planning for your Power Platform Solution
