Although not a function from the outset (And I think it should have been) ALM has been a definite focus for Microsoft, first with Dev Ops pipelines...
For further actions, you may consider blocking this person and/or reporting abuse
@wyattdave Love the post... "Every problem is an opportunity to invent new possibility"
Hi @wyattdave
Thank you again for an amazing solution, we tried implementing that but we are stuck while upgraging the solution via this flow. Even after settingbthe upgrade parameter, flow is successful but it is not doing anything to my solution.
Can you support if you have any insights.
Hi @plamba , sorry for late reply. Are you talking about updating the solution version. This has to be done before creating the export. You can patch the solution table with your new version and then when you export it will have the new version
Any support here from anyone?
Hey David this was a great post! It was so good that I joined the dev.to community right away!
Unfortunately, the pictures are not clear and it is difficult to replicate these flows to test them.
Would it be possible for you to somehow share all the actions expanded?
Maybe attach a PDF to this article or to a new one?
Thanks!!!!
Hi Oliver, let me see if I can find the solution and share it with you if that will help. It's a little out of date now as we can use the new Dataverse connectors across environments (so don't need to have in every environment now)
That would be awesome! And many thanks for answering so quickly!
This sounds like a great improvement! --> "we can use the new Dataverse connectors across environments (so don't need to have in every environment now)"
Ive uploaded it here, github.com/wyattdave/Power-Platfor.... Like I said its a bit out of date and will need some work to make it fit your setup but hopefully point you in the right direction. Any questions let me know 😊
This is awesome! Thank you David!
Will the above steps help to import the solution into all other environments?
Because based on your blog above it doesn't seems it will import solution into another environment from the environment this solution is deployed, Could you please point us in which place you're switching the environment for importing a solution?
Thank you.
The pipeline automatically exports and imports. But you have to have the pipeline solution deployed in all environments.
The Export flow is in the environment with the solution. The important flow is triggered in the environment you want to import it.
I use trigger conditions in the SharePoint list, each import flow uses an environment variable as the trigger. So on each import of the pipeline solution set the environment variable to it
Thank you, David for taking some time and replying to my query.
No problem, if you have any more questions let me know