Skip to content

Commit 4b4652f

Browse files
authored
Live publish
2 parents 5b58e2c + 1099131 commit 4b4652f

17 files changed

+7897
-8703
lines changed

.openpublishing.redirection.json

Lines changed: 7859 additions & 7804 deletions
Large diffs are not rendered by default.

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

Lines changed: 1 addition & 51 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Package a code component| Microsoft Docs
33
description: This article describes how to import code components into model-driven apps in Microsoft Dataverse.
44
ms.author: noazarur
55
author: noazarur-microsoft
6-
ms.date: 08/16/2022
6+
ms.date: 03/22/2023
77
ms.reviewer: jdaly
88
ms.topic: article
99
ms.subservice: pcf
@@ -103,56 +103,6 @@ To use the `push` capability, do the following:
103103
> [!NOTE]
104104
> 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.
105105
106-
## Create a solution project based on an existing solution in Dataverse
107-
108-
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:
109-
110-
1. Ensure that you have a valid authentication profile created.
111-
2. Run the command:
112-
113-
```CLI
114-
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>
115-
```
116-
117-
> [!NOTE]
118-
> Settings Values: autonumbering, calendar, customization, emailtracking, externalapplications, general, isvconfig, marketing, outlooksynchronization, relationshiproles, sales.
119-
120-
More information: [Settings options](/dotnet/api/microsoft.crm.sdk.messages.exportsolutionrequest)
121-
122-
> [!NOTE]
123-
> Manually publish the customizations if you are importing unmanaged solution.
124-
125-
## Create a plug-in project and add a reference to it in your solution
126-
127-
> [!NOTE]
128-
> The plugin command is in public preview and
129-
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:
130-
131-
1. Ensure that you have a valid authentication profile created.
132-
2. Navigate to the root directory where you want the project to be created.
133-
3. Run the [pac auth create](/power-platform/developer/cli/reference/auth) command:
134-
135-
```CLI
136-
pac auth create –url <https://xyz.crm.dynamics.com>
137-
```
138-
4. Run the [pac plugin init](/power-platform/developer/cli/reference/plugin) command to create the plug-in project
139-
140-
```CLI
141-
pac plugin init
142-
```
143-
144-
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.
145-
146-
```CLI
147-
pac solution add-reference –path <path to your plugin project>
148-
```
149-
150-
6. Run the command to build the solution and the referenced plug-in.
151-
152-
```CLI
153-
msbuild
154-
```
155-
156106
## Remove components from a solution
157107

158108
If you want to remove a code component from a solution file:

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

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Auto app updates (preview) | Microsoft Docs
33
description: Learn about the latest auto update feature for apps.
4-
ms.date: 08/05/2022
4+
ms.date: 03/22/2023
55
author: angela21k
66
ms.author: angelakim
77
ms.reviewer: jdaly
@@ -20,7 +20,7 @@ contributors:
2020

2121
[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
2222

23-
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.
23+
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.
2424

2525
> [!IMPORTANT]
2626
> - This is a preview feature.
@@ -30,14 +30,14 @@ Automatic updates in the preview will be limited to: 
3030

3131
- **Explicit tenant admin opt-in**: Tenant administrator user must opt-in from the Power Platform admin center to enable the feature.
3232

33-
- **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.
33+
- **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.
3434

3535
- **Dark hours only**: To further minimize impact, automatic updates will only happen during dark hours defined by either the customer or at geo level. 
3636

3737
## Enabling auto app update 
3838

3939
> [!NOTE]
40-
> 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.
40+
> 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.
4141
4242
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**.
4343

@@ -47,7 +47,10 @@ Automatic updates in the preview will be limited to: 
4747

4848
:::image type="content" source="media/auto-app-update-1.jpg" alt-text="Power Platform admin center environment settings":::
4949

50-
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.
50+
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.
51+
52+
> [!NOTE]
53+
> The drop-down list will only display publishers if you have a third-party application installed.
5154
5255
:::image type="content" source="media/auto-app-update-2.jpg" alt-text="Configure app update settings":::
5356

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

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,15 @@ Horizontal container control determines the position of the child components so
4949

5050
**Horizontal Overflow** - Defines whether the container shows scrollbars or remove content when it is too large to fit. **Scroll** and **Hide**.
5151

52+
**[RadiusBottomLeft](properties-size-___location.md)** – The degree to which the bottom-left corner of a control is rounded.
53+
54+
**[RadiusBottomRight](properties-size-___location.md)** – The degree to which the bottom-right corner of a control is rounded.
55+
56+
**[RadiusTopLeft](properties-size-___location.md)** – The degree to which the top-left corner of a control is rounded.
57+
58+
**[RadiusTopRight](properties-size-___location.md)** – The degree to which the top-right corner of a control is rounded.
59+
60+
5261
**Vertical Overflow** - Defines whether the container shows scrollbars or remove content when it is too large to fit. **Scroll** and **Hide**.
5362

5463
**Wrap** - Defines whether the content wraps to a new row or column when it cannot fit.

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

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,14 @@ Vertical container control determines the position of the child components so th
4949

5050
**Horizontal Overflow** - Defines whether the container shows scrollbars or remove content when it is too large to fit. **Scroll** and **Hide**.
5151

52+
**[RadiusBottomLeft](properties-size-___location.md)** – The degree to which the bottom-left corner of a control is rounded.
53+
54+
**[RadiusBottomRight](properties-size-___location.md)** – The degree to which the bottom-right corner of a control is rounded.
55+
56+
**[RadiusTopLeft](properties-size-___location.md)** – The degree to which the top-left corner of a control is rounded.
57+
58+
**[RadiusTopRight](properties-size-___location.md)** – The degree to which the top-right corner of a control is rounded.
59+
5260
**Vertical Overflow** - Defines whether the container shows scrollbars or remove content when it is too large to fit. **Scroll** and **Hide**.
5361

5462
**Wrap** - Defines whether the content wraps to a new row or column when it cannot fit.

powerapps-docs/maker/portals/release-updates.md

Lines changed: 0 additions & 65 deletions
This file was deleted.

powerapps-docs/maker/portals/versions/package-version-9.2.2103.md

Lines changed: 0 additions & 64 deletions
This file was deleted.

powerapps-docs/maker/portals/versions/package-version-9.2.2108.md

Lines changed: 0 additions & 52 deletions
This file was deleted.

0 commit comments

Comments
 (0)