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

[parvezghumra]

No description provided.

[learn-build-service-prod]

Learn Build status updates of commit d32dc31:

✅ Validation status: passed

File	Status	Preview URL	Details
power-platform/alm/devops-build-tool-tasks.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[learn-build-service-prod]

Learn Build status updates of commit 8aade08:

✅ Validation status: passed

File	Status	Preview URL	Details
power-platform/alm/devops-build-tool-tasks.md	✅Succeeded
power-platform/developer/cli/reference/solution.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[parvezghumra]

@microsoft-github-policy-service agree

[JimDaly]

You can't edit the developer/cli/reference/solution.md file.
As noted at the top of the file:

<!-- 
Do not edit this file. 
This file is generated by a program and any changes will be overwritten when this topic is re-generated.
Use the include files to add additional content to this topic.
-->

Please remove this change.

For this to change, the PAC CLI team must change the help text for the command. The new description will appear when the PAC CLI is updated and it will align with the description in the /help command.

[JimDaly]

@phecke and @marcelbf
The description for ImportSolution message ConvertToManaged property is found in our reference content too.

See:

• ImportSolutionRequest.ConvertToManaged Property:

  Direct the system to convert any matching unmanaged customizations into your managed solution.

• ImportSolution Action

  Converts any matching unmanaged customizations into your managed solution.

Web API also has ImportSolutionAsync Action with this property.

All these descriptions should be aligned.

Also, the remarks for the pac solution import command has this in the Remarks section: convert-to-managed

The convert-to-managed parameter doesn't take an unmanaged solution and import it as managed. This parameter allows a managed solution that is being imported into an environment convert unmanaged components to managed.

If this flag isn't explicitly set, the solution system will fail the import request because managed layers can't go on top of unmanaged base components. This switch allows the solution import to succeed and the net result is that the inbound managed solution will be the base layer for each of these components – the components in the destination environment are converted from being an unmanaged component to being a managed component.

Seems like current 'short description' for convert-to-managed is incorrect.

@parvezghumra you are proposing:

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.

Is the description used in other places equivalent to your intent? Or are you trying to describe a different behavior?

If it is the equivalent, please align your change with those existing descriptions.