Answered

Power Platform Set Solution Version: ##[error]Invalid number of components in version.

Like (0) Share

Report

Posted on 24 Nov 2021 18:39:49 by Community Power Pla...

Hi,

I want to update the version number of a Power Apps solution from within an Azure pipeline. However, the invalid number of components error is thrown at me.

Settings:

Task: Power Platform Set Solution Version
Solution Version Number: $(Build.BuildNumber)

Error:

##[error]Invalid number of components in version. Version: 18

Probably easy to fix, but I can't find my mistake if I compare my settings to the tutorial that I was following.

Kr,

Arthur

Categories:

Application Lifecycle Management (ALM)

All responses (3)

Answers (1)

AndrewElans 44 on 23 Mar 2023 at 16:05:57

Like (1)

Report

Re: Power Platform Set Solution Version: ##[error]Invalid number of components in version.

Ref. "Power Platform Set Solution Version" in Azure DevOps. Version : 2.0.17

Only the following params work smoothly based on my experience:

Solution Name: shall be the same as solution "Name" in Environment, otherwise gives error: "The solution: \'xxx\' is not found in the target Dataverse organization"

Solution Version Number: $(Build.BuildNumber) - shall be in format "x.x.x.x", works only if settings of pipeline -> "options" tab -> "Build number format" is filled in with something like $(Date:yyyy).$(Date:MM).$(Date:dd).$(Rev:rr), otherwise give the following error: "[ 'Error: Argument \'--solution-version\' is invalid. Unable to determine the version for \'2023032306\'.' ]"

Alternatively, Solution Version Number can be "1.0.0.$(Build.BuildNumber)" if "Build number format" is filled in with "$(Date:yyyyMMdd)$(Rev:rr)", or other variations considering template "x.x.x.x"

Related Links:

https://learn.microsoft.com/en-us/power-platform/alm/devops-build-tool-tasks#parameters-version
Part "While version number can be hardcoded in the pipeline, it is recommended to use an Azure DevOps pipeline variable like BuildId. This provides options to define the exact shape of version number under the "Options" tab, for example: $(Year:yyyy)-$(Month:MM)-$(Day:dd)-$(rev:rr)-3. This definition can then be used in the Set Solution Version task by setting the Version Number property with: $(Build.BuildId) instead of hard coding 20200824.0.0.2."

shall be rewritten in my opinion to: "While version number can be hardcoded in the pipeline, it is recommended to use an Azure DevOps pipeline variable like BuildNumber. This provides options to define the exact shape of version number under the "Options" tab, for example: $(Date:yyyy).$(Date:MM).$(Date:dd).$(rev:rr). This definition can then be used in the Set Solution Version task by setting the Version Number property with: $(Build.BuildNumber) instead of hard coding 2023.03.23.03."

https://learn.microsoft.com/en-us/azure/devops/pipelines/process/run-number

https://learn.microsoft.com/en-us/power-platform/developer/cli/reference/solution#pac-solution-online-version
command which is executed behind the tool to set solution name and version:
pac solution online-version --solution-name Samplesolution --solution-version 1.0.0.2
moshe raab 80 on 01 Jun 2022 at 13:31:43

Like (0)

Report

Re: Power Platform Set Solution Version: ##[error]Invalid number of components in version.

I need to do a similar thing, i.e. just increment the revision number.
In Options i set the Build Number Format to:
$(version.MajorMinor).$(version.Patch).$(Rev:r)

In the Power Platform Set Solution Version task i set the Solution Version Number to $Build.BuildNumber)

I get this error :
##[error]Invalid number of components in version. Version: $(version.MajorMinor).$(version.Patch).$(Rev:r). this should translate to: 1.0.0.2

what am i doing wrong?
Verified answer

Eline 25 on 25 Nov 2021 at 10:08:52

Like (0)

Report

Re: Power Platform Set Solution Version: ##[error]Invalid number of components in version.

Hi Meijrink,
You should set the Build number format in the options tab of the pipeline. That will solve the issue.