Difference between revisions of "Terminology"

From Power Wiki
Jump to navigation Jump to search
 
Line 12: Line 12:
  
 
=== About the CRM functionality from Microsoft ===
 
=== About the CRM functionality from Microsoft ===
First there were CRM, [[Microsoft Dynamics CRM]]. Then came Microsoft Dynamics 365 Customer Engagement (CE). Then came Power Apps and the former Microsoft Dynamics CRM/365 became customer engagement (model-driven) apps, built on Power Platform. Now we have customer engagement apps built on Power Platform, e.g. [[Dynamics 365 Sales]], [[Dynamics 365 Customer Service]] etc. The on-premise version still goes under the name Dynamics 365 CE.
+
First there were CRM, [[Microsoft Dynamics CRM]]. Then came Microsoft Dynamics 365 Customer Engagement (CE). Then came Power Apps and the former Microsoft Dynamics CRM/365 became customer engagement (model-driven) apps, built on Power Platform. These apps are also referred to as first-party model apps. Examples are [[Dynamics 365 Sales]] and [[Dynamics 365 Customer Service]]. The on-premise version still goes under the name Dynamics 365 CE.

Latest revision as of 13:50, 11 January 2021

This page contains information about the terminology related to Power Platform. The purpose is to give a quick overview of the terminology that is used.

Terminology changes within Dataverse. What we once knew as Entity, Field, Record, Option Set and Two Option are now Table, Column, Row, Choice and Yes/No. Terminology updates

About the CRM functionality from Microsoft

First there were CRM, Microsoft Dynamics CRM. Then came Microsoft Dynamics 365 Customer Engagement (CE). Then came Power Apps and the former Microsoft Dynamics CRM/365 became customer engagement (model-driven) apps, built on Power Platform. These apps are also referred to as first-party model apps. Examples are Dynamics 365 Sales and Dynamics 365 Customer Service. The on-premise version still goes under the name Dynamics 365 CE.