Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarified the purpose of the 'Convert to Managed' parameter on the 'Import Solution' task #2443

Closed
wants to merge 2 commits into from
Closed

Clarified the purpose of the 'Convert to Managed' parameter on the 'Import Solution' task #2443

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d32dc31
Update devops-build-tool-tasks.md
parvezghumra Feb 7, 2024
8aade08
Clarified purpose of Convert To Managed option in import solution com…
parvezghumra Feb 9, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion power-platform/alm/devops-build-tool-tasks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -191,7 +191,7 @@ steps:
| `HoldingSolution`<br/>Import as a holding solution | An advance parameter (true\|false) used when a solution needs to be upgraded. This parameter hosts the solution in Dataverse but does not upgrade the solution until the Apply Solution Upgrade task is run. |
| `OverwriteUnmanagedCustomizations`<br/>Overwrite un-managed customizations | Specify whether to overwrite un-managed customizations (true\|false). |
| `SkipProductUpdateDependencies`<br/>Skip product update dependencies | Specify whether the enforcement of dependencies related to product updates should be skipped (true\|false). |
| `ConvertToManaged`<br/>Convert to managed | Specify whether to import as a managed solution (true\|false). |
| `ConvertToManaged`<br/>Convert to managed | Specify whether to convert into managed any unmanaged versions of objects found in the target environment that exist in the solution being imported in a managed state (true\|false). |
| `AsyncOperation`<br/>Asynchronous import | If selected (**true**), the import operation will be performed asynchronously. This is recommended for larger solutions as this task will automatically timeout after 4 minutes otherwise. Selecting asynchronous will poll and wait until MaxAsyncWaitTime has been reached (true\|false). |
| `MaxAsyncWaitTime`<br/>Maximum wait time | Maximum wait time in minutes for the asynchronous operation; default is 60 min (1 hr), same as Azure DevOps default for tasks.|
| `PublishWorkflows`<br/>Activate processes after import | Specify whether any processes (workflows) in the solution should be activated after import (true\|false). |
Expand Down
4 changes: 2 additions & 2 deletions power-platform/developer/cli/reference/solution.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -404,7 +404,7 @@ This parameter requires no value. It's a switch.

#### `--convert-to-managed` `-cm`

Convert to a managed solution.
Convert into managed any unmanaged versions of objects found in the target Dataverse that exist in the solution being imported in a managed state.

This parameter requires no value. It's a switch.

Expand Down Expand Up @@ -891,4 +891,4 @@ Use one of these values:
### See also

[Microsoft Power Platform CLI Command Groups](index.md)<br />
[Microsoft Power Platform CLI overview](../introduction.md)
[Microsoft Power Platform CLI overview](../introduction.md)
Loading