Merge pull request #3804 from MicrosoftDocs/master

KumarVivek · web-flow · commit be9c07ff34ad · 2020-11-16T09:48:19.000-08:00
Live push
diff --git a/powerapps-docs/developer/common-data-service/includes/data-service-errors.md b/powerapps-docs/developer/common-data-service/includes/data-service-errors.md
@@ -448,7 +448,7 @@
 |0x80045030<br />-2147200976|Name: **CannotDeleteAttributeUsedInWorkflow**<br />Message: This attribute cannot be deleted because it is used in one or more workflows. Cancel any system jobs for workflows that use this attribute, then delete or modify any workflows that use the attribute, and then try to delete the attribute again.|
 |0x80048cfe<br />-2147185410|Name: **CannotDeleteBaseMoneyCalculationAttribute**<br />Message: The base money calculation Attribute is not valid for deletion|
 |0x8004022f<br />-2147220945|Name: **CannotDeleteCannedView**<br />Message: System-defined views cannot be deleted.|
-|0x80041d5a<br />-2147213990|Name: **CannotDeleteCDSUser**<br />Message: The Microsoft Dataverse User Role cannot be deleted.|
+|0x80041d5a<br />-2147213990|Name: **CannotDeleteCDSUser**<br />Message: The Microsoft Common Data Service User Role cannot be deleted.|
 |0x80061108<br />-2147086072|Name: **CannotDeleteChannelAccessProfileRule**<br />Message: You can't delete an active channel access profile rule. Deactivate the rule and then delete it.|
 |0x800608EB<br />-2147088149|Name: **CannotDeleteChannelProperty**<br />Message: You can’t delete a channel property which is being referred in a convert rule.|
 |0x80047016<br />-2147192810|Name: **CannotDeleteChildAttribute**<br />Message: The Child Attribute is not valid for deletion|
diff --git a/powerapps-docs/maker/canvas-apps/add-notifications.md b/powerapps-docs/maker/canvas-apps/add-notifications.md
@@ -58,29 +58,6 @@ In this article, the sample app used for notifications is built from the default
 
     ![Power Apps formula](./media/add-notifications/powerapps-function.png)
 
-## Perform an action when a user taps the notification
-
-### Pass parameters
-
-Your push notification can pass specific parameters to the app. For example, to read the **CaseID** value, use *Param("CaseID")*. To quickly identify this parameter, add a **Label** control to your app. Set the **Text** property of that control to **Param("CaseID")**. If the user opens the app from the **All apps** list, the value is empty. If the user opens the app from another ___location on the device, the value is populated with the **CaseID** value.
-
-### Set the start page
-
-You can set your app to open, for example, the **Case details** page as soon as the app opens:
-
-1. Add a **Timer** control, and set its **OnTimerEnd** property to this formula:
-
-    `Navigate(EditCase, ScreenTransition.None)`
-
-1. (optional) Hide the **Timer** control by setting its **Visible** property to **false**.
-
-1. Set the **OnVisible** property of the screen to **Timer.Start()**.
-
-> [!TIP]
-> It's a good idea to create a unique first page in the app for the notification:
-> 
-> 1. Create an empty page that your app doesn't already open, add a **Text Input** control, and set its **timer.Duration** value.
-> 2. When you create the app, set the timer to a non-zero value. When you're ready to publish the app, set the value to **0** to immediately trigger the timer.
 
 ## Syntax
 
diff --git a/powerapps-docs/maker/canvas-apps/data-platform-create-app-scratch.md b/powerapps-docs/maker/canvas-apps/data-platform-create-app-scratch.md
@@ -16,6 +16,8 @@ search.app:
 ---
 # Create a canvas app from scratch using Microsoft Dataverse
 
+[!INCLUDE[cc-data-platform-banner](../../includes/cc-data-platform-banner.md)]
+
 Build a canvas app to manage data that's stored in Dataverse, using standard entities (which are built in), custom entities (which your organization creates), or both.
 
 When you build an app from Dataverse, you don't need to create a connection from Power Apps, as you do with data sources such as SharePoint, Dynamics 365, or Salesforce. You need only to specify the entities that you want to show or manage in the app.
diff --git a/powerapps-docs/maker/model-driven-apps/share-model-driven-app.md b/powerapps-docs/maker/model-driven-apps/share-model-driven-app.md
@@ -143,7 +143,7 @@ These predefined roles are available with a [!INCLUDE [powerapps](../../includes
 |Environment Maker     |  None       | Can create new resources associated with an environment including apps, connections, custom APIs, gateways, and flows using Power Automate. However, does not have any privileges to access data within an environment. More information: [Environments overview](https://powerapps.microsoft.com/blog/powerapps-environments/)        |
 |System Administrator     |  Create, Read, Write, Delete, Customizations, Security Roles       | Has full permission to customize or administer the environment, including creating, modifying, and assigning security roles. Can view all data in the environment. More information: [Privileges required for customization](https://docs.microsoft.com/dynamics365/customer-engagement/customize/privileges-required-customization)        |
 |System Customizer     | Create (self), Read (self), Write (self), Delete (self), Customizations         | Has full permission to customize the environment. However, can only view rows for environment tables that they create. More information: [Privileges required for customization](https://docs.microsoft.com/dynamics365/customer-engagement/customize/privileges-required-customization)        |
-|Dataverse User     |  Read, Create (self), write (self), delete (self)       | Can run an app within the environment and perform common tasks for the rows that they own.        |
+|Common Data Service User     |  Read, Create (self), write (self), delete (self)       | Can run an app within the environment and perform common tasks for the rows that they own.        |
 |Delegate     | Act on behalf of another user        | Allows code to run as another user or impersonate.  Typically used with another security role to allow access to rows. More information: [Impersonate another user](https://docs.microsoft.com/dynamics365/customer-engagement/developer/org-service/impersonate-another-user)        |
 
 *Privilege is global scope unless specified otherwise.
diff --git a/powerapps-docs/mobile/media/para-image.png b/powerapps-docs/mobile/media/para-image.png
diff --git a/powerapps-docs/mobile/power-apps-mobile-notification.md b/powerapps-docs/mobile/power-apps-mobile-notification.md
@@ -112,14 +112,45 @@ When you trigger a push notification from a flow, you can send the notification
      - **Recipient Items-1**: Select how the flow is triggered.
      - **Message**: Enter the notification message.
      - **Open app**: Select whether to open the app or not when the user selects the notification.
-     - **Parameters**: Key-value parameters to pass with the notification. Your push notification can pass specific parameters to the app. These can be further processed in the app to open a specific page and load a specific state. For more information, see [Load a specific page and context when a user taps the notification](https://docs.microsoft.com/powerapps/maker/canvas-apps/add-notifications#load-a-specific-page-and-context-when-a-user-taps-the-notification).
+     - **Parameters**: Key-value parameters to pass with the notification. Your push notification can pass specific parameters to the app. These can be further processed in the app to open a specific page and load a specific state. For more information, see [Perform an action when a user taps the notification](power-apps-mobile-notification.md#perform-an-action-when-a-user-taps-the-notification).
 	 
      ![Enter the notification information](media/canvasapp-info.png)
 	
 8. When you're done, select **Save**. 
 9. Select **Flow checker** to check for error or warnings.
 10. Test the flow by selecting **Test** and follow the prompts. 
 
+## Perform an action when a user taps the notification
+
+### Pass parameters
+
+For canvas apps, you can pass key-value pairs using the **Parameters** field as JSON. For example, if you wanted to pass the CaseID, you would put the following as **Parameters**:
+` { "CaseID": 42 }`. You can also use dynamic values from earlier steps as shown below.
+
+![Sample parameters](media/para-image.png)
+
+### Read parameters
+
+To read the passed parameters, use Param("ParameterName"). For example, to read the **CaseID** value, use *Param("CaseID")*. To quickly identify this parameter, add a **Label** control to your app. Set the **Text** property of that control to **Param("CaseID")**. If the user opens the app from the **All apps** list, the value is empty. If the user opens the app from another ___location on the device, the value is populated with the **CaseID** value.
+
+### Set the start page
+
+You can set your app to open, for example, the **Case details** page as soon as the app opens:
+
+1. Add a **Timer** control, and set its **OnTimerEnd** property to this formula:
+
+    `Navigate(EditCase, ScreenTransition.None)`
+
+1. (optional) Hide the **Timer** control by setting its **Visible** property to **false**.
+
+1. Set the **OnVisible** property of the screen to **Timer.Start()**.
+
+> [!TIP]
+> It's a good idea to create a unique first page in the app for the notification:
+> 
+> 1. Create an empty page that your app doesn't already open, add a **Text Input** control, and set its **timer.Duration** value.
+> 2. When you create the app, set the timer to a non-zero value. When you're ready to publish the app, set the value to **0** to immediately trigger the timer.
+
 
 ## Known limitations
 
diff --git a/powerapps-docs/sample-apps/crisis-financial-impact-tracker/deploy-solution.md b/powerapps-docs/sample-apps/crisis-financial-impact-tracker/deploy-solution.md
@@ -152,7 +152,7 @@ to share apps with groups of users.
    > [!div class="mx-imgBorder"]
    > ![Share app](./media/share-app.png "Share app")
 
-1. Specify the Azure AD group or users who you want to share this app with. Because the app connects to Dataverse data, you also need to provide permissions to the entities. The sharing panel prompts you to manage security for the entities. Assign the **Higher Education Crisis Financial Impact Tracker User** and **Dataverse User** security roles to the entities used by this app, and then select **Share**.
+1. Specify the Azure AD group or users who you want to share this app with. Because the app connects to Dataverse data, you also need to provide permissions to the entities. The sharing panel prompts you to manage security for the entities. Assign the **Higher Education Crisis Financial Impact Tracker User** and **Common Data Service User** security roles to the entities used by this app, and then select **Share**.
 
    > [!div class="mx-imgBorder"]   
    > ![Assign roles](./media/assign-roles.png "Assign roles")
diff --git a/powerapps-docs/sample-apps/emergency-response/deploy-configure.md b/powerapps-docs/sample-apps/emergency-response/deploy-configure.md
@@ -316,7 +316,7 @@ groups to easily share apps with groups of users.
     > [!div class="mx-imgBorder"] 
     > ![Share canvas apps](media/conf-share-canvas-apps.png "Share canvas apps")
 
-4.  Specify the Azure AD group or users that you want to share this app with. As the app connects to Dataverse data, you will also need to provide permissions to the entities. The sharing panel prompts you to manage security for the entities. Assign the **Emergency Response User** and **Dataverse User** security roles to the entities used by this app and select **Share**.
+4.  Specify the Azure AD group or users that you want to share this app with. As the app connects to Dataverse data, you will also need to provide permissions to the entities. The sharing panel prompts you to manage security for the entities. Assign the **Emergency Response User** and **Common Data Service User** security roles to the entities used by this app and select **Share**.
 
     > [!div class="mx-imgBorder"] 
     > ![Share app with Azure AD group or users](media/conf-share-app-groups-users.png "Share app with Azure AD group or users")
diff --git a/powerapps-docs/teams/data-platform-compare.md b/powerapps-docs/teams/data-platform-compare.md
@@ -12,7 +12,9 @@ ms.reviewer: matp
 
 # How are Dataverse for Teams and Dataverse different?
 
-Applications within a team in Microsoft Teams have access to a Dataverse for Teams environment. Dataverse for Teams is a common platform that allows all these interfaces to have a unified understanding of how the data is modeled and consumed. Dataverse for Teams delivers a targeted set of the features commonly needed for creating apps, flows, and more within Teams. If your organization requires additional capabilities, such as more granular control for security and governance, or capacity beyond the approximately 1 million rows a Dataverse for Teams environment can contain, Dataverse for Teams can be promoted to Dataverse.
+[!INCLUDE[cc-data-platform-banner](../includes/cc-data-platform-banner.md)]
+
+Applications within a team in Microsoft Teams have access to a Dataverse for Teams environment. Dataverse for Teams is a common platform that allows all these interfaces to have a unified understanding of how the data is modeled and consumed. Dataverse for Teams delivers a targeted set of the features commonly needed for creating apps, flows, and more within Teams. If your organization requires additional capabilities, such as more granular control for security and governance, or capacity beyond the approximately 1 million rows a Dataverse for Teams environment can contain, Dataverse for Teams can be [upgraded](/power-platform/admin/about-teams-environment#upgrade-process) to Dataverse.
 
 ## Table features
 
@@ -88,7 +90,7 @@ Because Dataverse isn't specific to the Teams environment, it delivers more opti
 
 Integration with Dataverse for Teams is delivered primarily through connectors. Support for both standard connectors and the ability to use the Dataverse connector to connect to a Dataverse for Teams for a Teams environment is included. Users with Premium licenses have access to the full set of over 350 standard and premium connectors available. This provides the ability to bring data into or retrieve data from tables in Dataverse for Teams, execute workflows when data in those tables change, and also use data from tables in workflow logic.
 
-Dataverse can also use connectors. Additionally, Dataverse includes other built-in integration capabilities that can export data to a data lake or publish events to an event hub, service bus, or by using webhooks. Dataverse also supports the TDS protocol, which provides integration with SQL Server.<!--note from editor: Edit okay?-->
+Dataverse can also use connectors. Additionally, Dataverse includes other built-in integration capabilities that can export data to a data lake or publish events to an event hub, service bus, or by using webhooks. Dataverse also supports the TDS protocol, which provides integration with SQL Server.
 
 Dataverse can also be used with server-side sync to synchronize with Exchange or POP3, and with Data Export Service, which synchronizes data to Azure SQL Database.
 
diff --git a/powerapps-docs/teams/overview-data-platform.md b/powerapps-docs/teams/overview-data-platform.md
@@ -33,7 +33,7 @@ Some of the benefits of Dataverse for Teams include:
 
 - Support for up to 500 teams.
 
-- The capability to be promoted to Dataverse.
+- The capability to be upgraded to Dataverse.
 
 See also: [Dataverse for Teams FAQs](data-platform-faqs.md)
 
@@ -48,7 +48,7 @@ A solution often has multiple tables that are used together in an application. F
 You can create and populate these tables with a new visual editor that makes it even easier to work with these tables.
 
 > [!NOTE]
-> All the capabilities found in tables are powered by Dataverse for Teams. Although this will satisfy many situations, in some situations an organization might want to have additional capacity, capabilities, or control over their solution. In these scenarios, Dataverse for Teams environments can be upgraded to Microsoft Dataverse. The upgrade process, referred to as *promotion*, has several considerations discussed in [Promotion process](/power-platform/admin/about-teams-environment?branch=teams-preview#promotion-process) in the Microsoft Power Platform admin guide.
+> All the capabilities found in tables are powered by Dataverse for Teams. Although this will satisfy many situations, in some situations an organization might want to have additional capacity, capabilities, or control over their solution. In these scenarios, Dataverse for Teams environments can be upgraded to Microsoft Dataverse. The upgrade process has several considerations discussed in [Upgrade process](/power-platform/admin/about-teams-environment#upgrade-process) in the Microsoft Power Platform admin guide.
 
 ## Security in Dataverse for Teams
 
