Live publish

Author: buck1ey

powerapps-docs/developer/model-driven-apps/clientapi/send-in-app-notifications.md

@@ -1,7 +1,7 @@
 ---
 title: "Send in-app notifications within model-driven apps" 
 description: Learn how to configure notifications in model-driven apps by using a client API.
-ms.date: 01/30/2023
+ms.date: 02/22/2023
 ms.reviewer: jdaly
 ms.service: powerapps
 ms.subservice: mda-developer
@@ -35,18 +35,18 @@ To use the in-app notification feature, you need to enable the **In-app notifica
 
 1. Open the solution that contains the model-driven app.  
 
-1. Select the model-driven app and click **Edit** split menu to open using the modern app designer
+1. Select the model-driven app and click **Edit** split menu to open using the modern app designer.
 
-1. Open **Settings** and switch to **Upcoming**
+1. Open **Settings** and switch to **Features**.
 
-1. Enable "In-app notifications"
+1. Enable "In-app notifications".
 
     > [!div class="mx-imgBorder"]
     > ![Custom page as main page](media/send-in-app-notifications/app-designer-settings-enable-in-app-notifications.png "Custom page as main page")
 
-1. Click **Save** to save the settings change
+1. Click **Save** to save the settings change.
 
-1. Click **Publish** on the model-driven app
+1. Click **Publish** on the model-driven app.
 
 
 ## Send basic in-app notifications

powerapps-docs/maker/data-platform/azure-synapse-incremental-updates.md

@@ -45,7 +45,8 @@ Azure Synapse Link for Dataverse. This guide assumes that you have already met t
 ## Connect Dataverse to Synapse workspace with incremental folder enabled 
 
 1. Sign in to [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc) and select your environment.
-1. On the left navigation pane, select **Dataverse**, select **Azure Synapse Link**, and then on the command bar, select **+ New link**.
+1. On the left navigation pane,  select **Azure Synapse Link**. [!INCLUDE [left-navigation-pane](../../includes/left-navigation-pane.md)] 
+1. On the command bar, select **+ New link**.
 1. Select the **Subscription**, **Resource group**, and **Storage account**. Select **Next**.  
 1. Add the tables you want to export, and then select **Advanced**.  
 1. Turn on **Show advanced configuration settings** and **Enable Incremental Update Folder Structure**.

powerapps-docs/maker/data-platform/azure-synapse-link-data-lake.md

@@ -52,17 +52,14 @@ You can use the Azure Synapse Link to connect your Microsoft Dataverse data to A
 ## Connect Dataverse to Azure Data Lake Storage Gen2
 
 1. Sign in to [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc) and select your preferred environment.
-
-2. On the left navigation pane, select **Data**, select **Azure Synapse Link**, and then on the command bar, select **+ New link to data lake**.
-
-    ![Navigate to Power Apps.](media/navigate-to-powerapps.png "Navigate to Power Apps")
-
-3. Select the **Subscription**, **Resource group**, and **Storage account**. Ensure that storage account meets the requirements specified in the [Prerequisites](#prerequisites) section. Select **Next**.
+1. On the left navigation pane, select **Azure Synapse Link**. [!INCLUDE [left-navigation-pane](../../includes/left-navigation-pane.md)]
+1. On the command bar, select **+ New link to data lake**.
+1. Select the **Subscription**, **Resource group**, and **Storage account**. Ensure that storage account meets the requirements specified in the [Prerequisites](#prerequisites) section. Select **Next**.
 
     > [!NOTE]
     > As part of linking the environment to a data lake, you grant the Azure Synapse Link service access to your storage account. Ensure that you followed the [prerequisites](#prerequisites) of creating and configuring the Azure data lake storage account, and granting yourself an owner role on the storage account. Additionally, you grant the Power Platform Dataflows service access to your storage account. More information: [Self-service data prep with dataflows](self-service-data-prep-with-dataflows.md).  
 
-4. Add the tables you want to export, and then select **Save**. Only tables with change tracking enabled can be exported. More information: [Enable change tracking](/dynamics365/customer-engagement/admin/enable-change-tracking-control-data-synchronization).
+1. Add the tables you want to export, and then select **Save**. Only tables with change tracking enabled can be exported. More information: [Enable change tracking](/dynamics365/customer-engagement/admin/enable-change-tracking-control-data-synchronization).
 
    ![Select tables for export.](media/export-data-lake-select-entity.png "Select tables for export")
 

powerapps-docs/maker/data-platform/azure-synapse-link-solution.md

@@ -42,20 +42,20 @@ This section describes the prerequisites necessary to transport the Azure Synaps
 > The Azure Synapse Link for Dataverse solution must be installed in both the source and the destination environments.
 
 1. Sign into [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc), and then select the source environment for the Azure Synapse Link for Dataverse configuration.
-
-2. On the left navigation pane, select **Solutions** > **Open AppSource**.
+1. On the left navigation pane, select **Solutions**. [!INCLUDE [left-navigation-pane](../../includes/left-navigation-pane.md)]
+1. Select **Open AppSource**.
 
     ![Open App Source](media/open-app-source.png "Open App Source")
 
-3. Select for the solution named **Azure Synapse Link for Dataverse**, and then select **Get it now**.
+1. Select for the solution named **Azure Synapse Link for Dataverse**, and then select **Get it now**.
 
     ![Azure Synapse Link for Dataverse Solution](media/asl-solution.png "Azure Synapse Link for Dataverse Solution")
 
 4. Repeat above steps in the destination environment. You need the **Azure Synapse Link for Dataverse** solution in both the source and destination environments.
 
 ## Add an Azure Synapse Link configuration to a solution
 
-1. Sign into [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc), select the source environment, and then on the left navigation pane, select **Solutions**.
+1. Sign into [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc), select the source environment, and then on the left navigation pane, select **Solutions**. [!INCLUDE [left-navigation-pane](../../includes/left-navigation-pane.md)]
 
 2. Select **New solution**. Provide a **Name**, **Publisher**, and **Version Number**.  
 

powerapps-docs/maker/data-platform/azure-synapse-link-synapse.md

@@ -56,21 +56,17 @@ You can use the Azure Synapse Link to connect your Microsoft Dataverse data to A
 ## Connect Dataverse to Synapse workspace
 
 1. Sign in to [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc) and select your preferred environment.
-
-2. On the left navigation pane, select **Data**, select **Azure Synapse Link**, and then on the command bar, select **+ New link**.
-
-    ![Navigate to Power Apps.](media/navigate-to-powerapps.png "Navigate to Power Apps")
-
-3. Select the **Connect to your Azure Synapse workspace** option.
-
-4. Select the **Subscription**, **Resource group**, **Workspace name**, and **Storage account**. Ensure that the Synapse workspace and storage account meet the requirements specified in the [Prerequisites](#prerequisites) section. Select **Next**.
+1. On the left navigation pane, select **Azure Synapse Link**. [!INCLUDE [left-navigation-pane](../../includes/left-navigation-pane.md)]
+1. On the command bar, select **+ New link**.
+1. Select the **Connect to your Azure Synapse workspace** option.
+1. Select the **Subscription**, **Resource group**, **Workspace name**, and **Storage account**. Ensure that the Synapse workspace and storage account meet the requirements specified in the [Prerequisites](#prerequisites) section. Select **Next**.
 
     ![Connect to your workspace.](media/connect-to-workspace.png "Connect to your workspace")
 
     > [!NOTE]
     > As part of linking the environment to a data lake, you grant the Azure Synapse Link service access to your storage account. Ensure that you followed the [prerequisites](#prerequisites) of creating and configuring the Azure data lake storage account, and granting yourself an owner role on the storage account. Additionally, you grant the Power Platform Dataflows service access to your storage account. More information: [Self-service data prep with dataflows](self-service-data-prep-with-dataflows.md).  
 
-5. Add the tables you want to export, and then select **Save**. Only tables with change tracking enabled can be exported. More information: [Enable change tracking](/dynamics365/customer-engagement/admin/enable-change-tracking-control-data-synchronization).
+1. Add the tables you want to export, and then select **Save**. Only tables with change tracking enabled can be exported. More information: [Enable change tracking](/dynamics365/customer-engagement/admin/enable-change-tracking-control-data-synchronization).
 
     ![Add tables.](media/add-tables.png "Add tables")
 
@@ -79,14 +75,14 @@ You can follow the steps above to create a link from one environment to multiple
 > [!NOTE]
 > The data exported by Azure Synapse Link service is encrypted at transit using Transport Layer Security(TLS) 1.2 or higher and encrypted at rest in Azure Data Lake Storage Gen2. Additionally, transient data in the blob storage is also encrypted at rest. Encryption in Azure Data Lake Storage Gen2 helps you protect your data, implement enterprise security policies, and meet regulatory compliance requirements. More information: [Azure Data Encryption-at-Rest]( /azure/security/fundamentals/encryption-atrest)
 >
-> Currently, you can't provide public IPs for the Azure Synapse Link for Dataverse service that can be used in **Azure Data Lake firewall settings**. Public IP network rules have no effect on requests originating from the same Azure region as the storage account. Services deployed in the same region as the storage account use private Azure IP addresses for communication. Thus, you can't restrict access to specific Azure services based on their public outbound IP address range.
+> Currently, you can't provide public IP addresses for the Azure Synapse Link for Dataverse service that can be used in **Azure Data Lake firewall settings**. Public IP network rules have no effect on requests originating from the same Azure region as the storage account. Services deployed in the same region as the storage account use private Azure IP addresses for communication. Thus, you can't restrict access to specific Azure services based on their public outbound IP address range.
 More information: [Configure Azure Storage firewalls and virtual networks]( /azure/storage/common/storage-network-security)
 
 ## Manage table data to the Synapse workspace
 
 After you have set up the Azure Synapse Link, you can manage the tables that are exported in one of two ways:
 
-- On the Power Apps maker portal **Azure Synapse Link** area, select **Manage tables** on the command bar to add or remove one or more linked tables.
+- In the Power Apps (make.powerapps.com) **Azure Synapse Link** area, select **Manage tables** on the command bar to add or remove one or more linked tables.
 - On the Power Apps maker portal **Tables** area, select **…** next to a table, and then select the linked data lake where you want to export table data.
 
    ![Select a table for export.](media/select-entity-export.png "Select a table for export")

powerapps-docs/maker/data-platform/create-and-use-dataflows.md

@@ -75,15 +75,9 @@ it.
 
     ![Environment switcher.](media/environment-switcher.png)
 
-2.  On the left navigation pane, select the down arrow next to **Data**.
-
-    ![Data select.](media/data-select.png)
-
-3.  In the **Data** list, select **Dataflows**, select **New dataflow**, and then select **Start from blank**.
-
-    ![Create a dataflow.](media/create-a-dataflow.png)
-
-4.  On the **New Dataflow** page enter a **Name** for the dataflow. By default, dataflows store tables in Dataverse. Select **Analytical entities only** if you want tables to be stored in your organization's Azure Data Lake storage account. Select **Create**. 
+1. On the left navigation pane, select **Dataflows**. [!INCLUDE [left-navigation-pane](../../includes/left-navigation-pane.md)]
+1. select **New dataflow**, and then select **Start from blank**.
+1. On the **New Dataflow** page enter a **Name** for the dataflow. By default, dataflows store tables in Dataverse. Select **Analytical entities only** if you want tables to be stored in your organization's Azure Data Lake storage account. Select **Create**. 
 
      > [!IMPORTANT]
      > There is only one owner of any dataflow—the person who created it. Only the owner can edit the dataflow. Authorization
@@ -94,16 +88,16 @@ it.
      > accessible via the Power Platform Dataflow connector and access to it requires
      > membership within the environment it was created in.
 
-5. On the **Choose data source** page, select the data source where the tables are stored. The selection of data sources displayed allows you to create dataflow tables. 
+1. On the **Choose data source** page, select the data source where the tables are stored. The selection of data sources displayed allows you to create dataflow tables. 
 
     ![Choose a data source.](media/choose-data-source.png)
 
-6. After you select a data source, you’re prompted to provide the connection
+1. After you select a data source, you’re prompted to provide the connection
 settings, including the account to use when connecting to the data source. Select **Next**.
 
     ![Connect to data source.](media/data-source-provide-cred.png)
 
-7. Once connected, you select the data to use for your table. When you
+1. Once connected, you select the data to use for your table. When you
 choose data and a source, the Power Platform Dataflow service will subsequently
 reconnect to the data source in order to keep the data in your dataflow
 refreshed, at the frequency you select later in the setup process.
@@ -115,6 +109,7 @@ Now that you've selected the data to use in the table, you can use the dataflow
 shape or transform that data into the format necessary for use in your dataflow.
 
 ## Use the dataflow editor to shape or transform data
+
 You can shape your data selection into a form that works best for your table using a
 Power Query editing experience, similar to the Power Query Editor in Power BI
 Desktop. To learn more about Power Query, see [Query overview in Power BI Desktop](/power-bi/desktop-query-overview).

powerapps-docs/maker/data-platform/create-custom-entity.md

@@ -38,12 +38,9 @@ Sign in to [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium
 
 ## Create a custom table
 
-1. On the left navigation pane expand **Data**, select **Tables**, and then select **New table**.
-
-    > [!div class="mx-imgBorder"] 
-    > ![New table.](media/create-custom-entity/create-new-entity.png)
-
-2. In the right pane, enter the following values, and then select **Create**.
+1. On the left navigation pane select **Tables**. [!INCLUDE [left-navigation-pane](../../includes/left-navigation-pane.md)]
+1. On the command bar select **New table**.
+1. In the right pane, enter the following values, and then select **Create**.
 
     - **Display name**: *Pet* 
     - **Description**: *Custom table to track pet services*
@@ -135,7 +132,8 @@ Skip this step if you only want to use the Pet table in a canvas app.
 
 1. Select **Back** to close the view designer and return to Power Apps.
 
-1. On the left navigation pane, expand **Data**, select **Tables**, and then select **Pet**.
+1. On the left navigation pane, select **Tables**. [!INCLUDE [left-navigation-pane](../../includes/left-navigation-pane.md)]
+1. Select **Pet**.
 
 1. In the **Pet** table, select the **Forms** area, and then select **Information** next to the **Main** form type to open the form designer.
 

powerapps-docs/maker/data-platform/create-custom-help-pages.md

@@ -152,12 +152,14 @@ Author needs to define the target through drag and drop capability in the proper
 All help content is stored in a help page component in Dataverse as part of your solution. When you move your solution from one environment to another, such as from test to production, you can define that your help rows are exported so that they are included in the solution. This enables you to keep your help content in sync with features in your solution as it moves to different environments. As a part of your solution, custom help panes support all standard solution application lifecycle management (ALM) features.
 
 ### Moving content via solutions
+
 By default, all new help pages appear in the default solution. If you want to move your content to another environment, first add your existing help pages into an unmanaged solution before you export them. To add a help page to an unmanaged solution, follow these steps:
 
 1. Sign into [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc).
-2. On the left navigation pane, select **Solutions** and then open the unmanaged solution you want.
-3. Select **Add Existing** on the command bar, and then select **Help Page**.
-4. Select the help pages that you want to add, and then select **Add**. More information: [Export solutions](export-solutions.md)
+1. On the left navigation pane, select **Solutions**. [!INCLUDE [left-navigation-pane](../../includes/left-navigation-pane.md)]
+1. Open the unmanaged solution you want.
+1. Select **Add Existing** on the command bar, and then select **Help Page**.
+1. Select the help pages that you want to add, and then select **Add**. More information: [Export solutions](export-solutions.md)
 
 ## Help page documentation automation