Unanswered

Issue in solution version of power platform tools in azure devops

(0) Share

Report

Posted on by Sanjay_Ramaling

Hi Power Users,

I am trying a configure CI pipeline in azure DevOps , i am currently using power platform set solution version provided in classic editor of azure DevOps.

The requirement is i want to parse my power apps solution version into the power platform set solution version component as variable , i am not able to do so , i am not able find the documentation as well.

to give in simple terms,

the pipeline should pick the solution version of power app from ui .we we are in (1.0.0.15) version of the app , this has to be dynamically populated in set solution version in power platform build tools and incremented every time i run the pipeline

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (3)

Answers (0)

Parvez Ghumra 1,579 Moderator on at

Like (0)

Report

@Sanjay_Ramaling If I understand you correctly, I think you're trying to set the solution version dynamically based on the existing version number of the solution. Like an auto-incrementing logic whenever a change is made/attempted to be committed? Please correct me if I'm wrong.

I think you will have to write your custom custom logic to retrieve the current version number of the target solution, and hold this value in memory before deriving the new version number from it and passing this value as an input parameter into the Set Solution Version number task

Was this reply helpful? Yes No
Sanjay_Ramaling 6 on at

Like (0)

Report

Thanks @parvezghumra is the current solution version saved in table or where do you take this field from. If you can share a small script to get current solution version number. I can take care of rest

Was this reply helpful? Yes No
cchannon 4,702 Moderator on at

Like (0)

Report

I believe you can manually edit the 'current version' just by adding entries to the SolutionHistoryData table (link) but I have never done it myself so you should exercise caution: this is DEFINITELY something you should only try in a disposable dev environment.

Was this reply helpful? Yes No