Power Platform Build Tools automate common build and deployment tasks related to Power Platform. This includes synchronization of solution metadata (a.k.a. solutions) between development environments and source control, generating build artifacts, deploying to downstream environments, provisioning/de-provisioning of environments, and the ability to perform static analysis checks against your solution using the PowerApps checker service.
When cloning a solution there are parameters to specify solution type and localization settings for the solution but those values don't get included in the cdsproj that is generated and the PropertyGroup section is commented out by default.
Additionally, these parameters don't exist for pac solution init but default values are generated in the cdsproj and also commented.
Ideally, the PropertyGroup would not be commented and would take default values if not supplied but otherwise should follow the values used in the command. Also, the options for packagetype and localize would be available in the solution init command as well
Steps to reproduce:
CLONE:
Connect to your Dataverse environment by using the pac auth command. For more information, see Connect to your tenant.
Run the following command to clone an existing solution to your local machine:
pac solution clone --name <solutionName> --packagetype Both --localize
Replace <solutionName> with the name of the solution you want to clone.
Navigate to the newly created solution folder and open the solution folder and open the src\.cdsproj file
The following PropertyGroup exists but is commented and the value(s) supplied for packagetype and localization don't match
INIT:
Navigate to the directory on your machine where you want your repository to exist locally and run the following command:
Replace <publisherName> with the name of the publisher for the solution. For more information on solution publishers, see Solution publisher.
Replace <publisherPrefix> with the publisher prefix for the solution. A prefix is used to uniquely identify custom components in a solution.
Replace <solutionName> with the name of your new solution.
Navigate to the newly created solution folder and open the solution folder and open the src\.cdsproj file
The following PropertyGroup exists but is commented and the value(s) supplied for packagetype and localization don't match
When cloning a solution there are parameters to specify solution type and localization settings for the solution but those values don't get included in the cdsproj that is generated and the PropertyGroup section is commented out by default.
Additionally, these parameters don't exist for pac solution init but default values are generated in the cdsproj and also commented.
Ideally, the PropertyGroup would not be commented and would take default values if not supplied but otherwise should follow the values used in the command. Also, the options for packagetype and localize would be available in the solution init command as well
Steps to reproduce: CLONE:
<solutionName>with the name of the solution you want to clone.The following PropertyGroup exists but is commented and the value(s) supplied for packagetype and localization don't match
INIT:
<publisherName>with the name of the publisher for the solution. For more information on solution publishers, see Solution publisher.<publisherPrefix>with the publisher prefix for the solution. A prefix is used to uniquely identify custom components in a solution. Replace<solutionName>with the name of your new solution.The following PropertyGroup exists but is commented and the value(s) supplied for packagetype and localization don't match