Merge remote-tracking branch 'origin/main' into matp-3233112

Author: Mattp123

.openpublishing.redirection.json

@@ -3,7 +3,7 @@ title: Package a code component| Microsoft Docs
 description: This article describes how to import code components into model-driven apps in Microsoft Dataverse.
 ms.author: noazarur
 author: noazarur-microsoft
-ms.date: 08/16/2022
+ms.date: 03/22/2023
 ms.reviewer: jdaly
 ms.topic: article
 ms.subservice: pcf
@@ -103,56 +103,6 @@ To use the `push` capability, do the following:
    > [!NOTE]
    > The publisher prefix that you use with the `push` command should match the publisher prefix of your solution in which the components will be included.
 
-## Create a solution project based on an existing solution in Dataverse
-
-To create a solution project based on an existing solution in Dataverse, run the [pac solution clone](/power-platform/developer/cli/reference/solution) command.. To do so:
-
-1. Ensure that you have a valid authentication profile created.
-2. Run the command:
-
-   ```CLI
-   pac solution clone –-name(-n) <name of the solution to be exported> --targetversion(-v) <version of your solution> --include(-i) <settings that should be included>
-   ```
-
-   > [!NOTE]
-   > Settings Values: autonumbering, calendar, customization, emailtracking, externalapplications, general, isvconfig, marketing, outlooksynchronization, relationshiproles, sales.
-
-More information: [Settings options](/dotnet/api/microsoft.crm.sdk.messages.exportsolutionrequest)
-
-> [!NOTE]
-> Manually publish the customizations if you are importing unmanaged solution.
-
-## Create a plug-in project and add a reference to it in your solution
-
-> [!NOTE]
-> The plugin command is in public preview and 
-Microsoft Power Platform CLI now supports creating a plug-in project and packaging it in a solution by adding a reference to the plug-in project. The [pac plugin init](/power-platform/developer/cli/reference/plugin) command creates the template files (csproj, Plugin.cs & ServiceHelper.cs) in the directory. To do so: 
-
-1. Ensure that you have a valid authentication profile created.
-2. Navigate to the root directory where you want the project to be created.
-3. Run the [pac auth create](/power-platform/developer/cli/reference/auth) command:
-
-   ```CLI
-   pac auth create –url <https://xyz.crm.dynamics.com>
-   ```
-4. Run the [pac plugin init](/power-platform/developer/cli/reference/plugin) command to create the plug-in project
-
-   ```CLI
-   pac plugin init
-   ```
-
-5. Add a reference to your solution project  using the [pac solution add-reference](/power-platform/developer/cli/reference/solution) command so that the plug-in project gets built when the solution is built.
-
-   ```CLI
-   pac solution add-reference –path <path to your plugin project>
-   ```
-
-6. Run the command to build the solution and the referenced plug-in.
-
-   ```CLI
-   msbuild
-   ```
-
 ## Remove components from a solution
 
 If you want to remove a code component from a solution file:

powerapps-docs/developer/component-framework/import-custom-controls.md

@@ -1,7 +1,7 @@
 ---
 title: Auto app updates (preview) | Microsoft Docs
 description: Learn about the latest auto update feature for apps.
-ms.date: 08/05/2022
+ms.date: 03/22/2023
 author: angela21k
 ms.author: angelakim
 ms.reviewer: jdaly
@@ -20,7 +20,7 @@ contributors:
 
 [!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
 
-Auto app update feature allows automatic updates of applications installed through AppSource. This feature helps both publishers and customers keep software up to date in a simple and controlled way with minimal administrative overhead. 
+Auto app update feature allows automatic updates of third-party applications installed through AppSource. This feature helps both third-party  publishers and customers keep software up to date in a simple and controlled way with minimal administrative overhead.
 
 > [!IMPORTANT]
 > - This is a preview feature.
@@ -30,14 +30,14 @@ Automatic updates in the preview will be limited to: 
 
 - **Explicit tenant admin opt-in**: Tenant administrator user must opt-in from the Power Platform admin center to enable the feature.
 
-- **Pre-approved publishers**: Tenant administrator user must indicate which publishers are permitted to automatically update apps in their environment once opted-in from the Power Platform admin center.
+- **Pre-approved publishers**: Tenant administrator user must indicate which third-party publishers are permitted to automatically update apps in their environment once opted-in from the Power Platform admin center.
 
 - **Dark hours only**: To further minimize impact, automatic updates will only happen during dark hours defined by either the customer or at geo level.  
 
 ## Enabling auto app update  
 
 > [!NOTE]
-> Publishers do not require additional action to enable automatic updates for their apps. Only tenant admin users are required to act if they want to opt-in to this feature for select publishers.
+> Publishers do not require additional action to enable automatic updates for their apps. Only tenant admin users are required to act if they want to opt-in to this feature for select third-party publishers.
 
 1. Log into the [Power Platform admin center](https://admin.powerplatform.microsoft.com) as an administrator user. From the Environments page, select an environment and click on **Settings**.
 
@@ -47,7 +47,10 @@ Automatic updates in the preview will be limited to: 
 
    :::image type="content" source="media/auto-app-update-1.jpg" alt-text="Power Platform admin center environment settings":::
 
-1. Toggle the configurator to **'On'** to opt-in to the feature.  From the drop-down list of publishers, select for which publishers you want to automatically update apps.
+1. Toggle the configurator to **'On'** to opt-in to the feature.  From the drop-down list of publishers, select for which third-party publishers you want to automatically update apps.
+
+   > [!NOTE]
+   > The drop-down list will only display publishers if you have a third-party application installed.
 
    :::image type="content" source="media/auto-app-update-2.jpg" alt-text="Configure app update settings":::
 

powerapps-docs/developer/data-platform/isv-app-management-autoupdate.md

@@ -49,6 +49,15 @@ Horizontal container control determines the position of the child components so
 
 **Horizontal Overflow** - Defines whether the container shows scrollbars or remove content when it is too large to fit. **Scroll** and **Hide**.
 
+**[RadiusBottomLeft](properties-size-___location.md)** – The degree to which the bottom-left corner of a control is rounded.
+
+**[RadiusBottomRight](properties-size-___location.md)** – The degree to which the bottom-right corner of a control is rounded.
+
+**[RadiusTopLeft](properties-size-___location.md)** – The degree to which the top-left corner of a control is rounded.
+
+**[RadiusTopRight](properties-size-___location.md)** – The degree to which the top-right corner of a control is rounded.
+
+
 **Vertical Overflow** - Defines whether the container shows scrollbars or remove content when it is too large to fit. **Scroll** and **Hide**.
 
 **Wrap** -  Defines whether the content wraps to a new row or column when it cannot fit.

powerapps-docs/maker/canvas-apps/controls/control-horizontal-container.md

@@ -49,6 +49,14 @@ Vertical container control determines the position of the child components so th
 
 **Horizontal Overflow** - Defines whether the container shows scrollbars or remove content when it is too large to fit. **Scroll** and **Hide**.
 
+**[RadiusBottomLeft](properties-size-___location.md)** – The degree to which the bottom-left corner of a control is rounded.
+
+**[RadiusBottomRight](properties-size-___location.md)** – The degree to which the bottom-right corner of a control is rounded.
+
+**[RadiusTopLeft](properties-size-___location.md)** – The degree to which the top-left corner of a control is rounded.
+
+**[RadiusTopRight](properties-size-___location.md)** – The degree to which the top-right corner of a control is rounded.
+
 **Vertical Overflow** - Defines whether the container shows scrollbars or remove content when it is too large to fit. **Scroll** and **Hide**.
 
 **Wrap** -  Defines whether the content wraps to a new row or column when it cannot fit.