Activity entities within the Common Data Service / Dynamics 365 have traditionally been…problematic at the best of times. While an entirely useful construct when working from a functional standpoint in the application, their backend structure can cause some challenges when evaluating more technical requirements. A lot of this comes down to their unique characteristics. For example, all default…
Continue Reading The CRM Chap’s Article on their blog
Changing Common Data Service Task Entity Ownership in a Canvas Power App
Activity entities within the Common Data Service / Dynamics 365 have traditionally been…problematic at the best of times. While an entirely useful construct when working from a functional standpoint in the application, their backend structure can cause some challenges when evaluating more technical requirements. A lot of this comes down to their unique characteristics.
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
