References & Glossary for the 5 pitfalls...

Owned by thierry sinassamy
Last updated: May 27, 2022
2 min read

References

[1] Dynamics CRM / 365 – from Dynamics CRM 2011 to Dynamics 365 (on-premises V.9.0, online V.9.1)

 [2] Execution contexts – Regardless, the technology or the product: Dynamics CRM / Dynamics 365 could be a source as a database, Dynamics 365 could be a destination as a database or a service (online).

 [3] POA (Principal Object Access) - POA table stores information about sharing of records in CRM. Every time shares are granted on records in CRM, a new entry is created in POA table. It stores information of User/Team with the record is stored, Object GUID, rights granted, etc.

 [4] Webhooks : Information available in Microsoft Docs (https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/use-webhooks).

 

Glossary

CRM solutions – “Solutions are how customizers and developers author, package, and maintain units of software that extend Dynamics 365 for Customer Engagement” (Introduction to solutions (Developer Guide for Dynamics 365 Customer Engagement (on-premises)) | Microsoft Docs)

CRM system maintenance – “By default CRM will create six maintenance jobs which are scheduled to run daily. These jobs are executed by the Microsoft Dynamics CRM Asynchronous Processing Service (maintenance).  Depending on when the organization was created the maintenance jobs may run right when users are in the system….” (When Dynamics CRM Async maintenance job runs, deadlock occur on Alter Index Command - Stack Overflow)

Denormalization - A database optimization technique or mechanism in which we add redundant data to one or more tables. 

Dynamics 365 App for Outlook - Dynamics 365 App for Outlook is an Outlook add-in that uses Exchange Web Services (EWS) to interact with Microsoft Exchange. This requires OAuth be enabled on Microsoft Exchange. (Deploy Dynamics 365 App for Outlook | Microsoft Docs)

Pitfall – As Dynamics CRM / 365 (online/on-premises) is a black box, pitfall could be considered as an unexpected difficulty during data migration process to overcome.

Webhook – “Webhooks enable developers and ISV’s to integrate Customer Engagement data with their own custom code hosted on external services. By using the webhook model, you can secure your endpoint by using authentication header or query string parameter keys.” (https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/use-webhooks )