How DevOps Release pipeline handling dependency ?

(1) Share

Report

Posted on by Axal

945

Hello guys,

When releasing (publish) solution to other environment lets say new environment, how DevOps can handle he dependency of that new solution ? For example : I have a Power App Solution which when about to install / imported to new environment there are some solution need to be exist already. And actually all the solutions already in my Azure Artifact which will be pull in the Release pipeline, its just I presumed when the Release want to import my solution, it is not import those "pre-requisites" solution first, which is my solution dependent with. So, I have a whole lots of error about missing dependency.

Kindly advice what is the correct way of doing this.

Thanks

Categories:

Application Lifecycle Management (ALM)

Power Platform Build Tools

All responses (1)

Answers (0)

Community Power Pla... on at

Like (0)

Report

Re: How DevOps Release pipeline handling dependency ?

I have the same issue. I've had issues like this when manually importing/exporting solutions, and I believe it gets resolved by clicking on each flow in the solution and then +Add required components. Like you, I am now trying to figure out how the build tools can automatically do this for me.

EDIT: As expected, clicking on +Add required components for every flow eliminates my missing dep issue. How can I automate that part?