Deployment Process of Solutions

(0) Share

Report

Posted on by hazer_kirbasogl

Hello,

I have some confusings about deployment process of Powerapps solutions,

Me and my team members are trying to find work-around about simultaneously work for tasks in same project,

We have created our dev environments as developer type of environments(separated), we have separated branches at devops and pipelines for exporting and packing solution to the branch.

Our Environment List is ;

(Developer 1 Environment, Developer 2 Environment, Common DEV, TEST, PROD 1, PROD 2 'region base')

When we are trying to pull our requests to main branch, there are some conflicts pop-up like in screenshot,

Even we have not been working same components, we see that conflicts for that and merging that really consume too much time,

What is the correct approach for working simultaneously in solutions at Powerapps?

I could not find useful documentations about it maybe because of the way is not correct 🙂

Thanks from now answers,

Hazer.

Categories:

Governance & administering

I have the same question (0)

All responses (6)

Answers (0)

Sort by

cavitha 50 on at

Like (0)

Report
Copy link

Link copied!

Currently Power Platform is not designed to work with multiple developers to work on a single app. I would suggest that each of your team members work on various artefacts of the solution. There are announcements in Power Platform conference which will be released in coming months
- https://powerapps.microsoft.com/en-us/blog/power-apps-brings-collaboration-to-center-stage-with-3-big-announcements/

Was this reply helpful? Yes No
hazer_kirbasogl 9 on at

Like (0)

Report
Copy link

Link copied!

Actually, Im not fully mentioning Powerapps, i mean a little bit about solution deployment. How we can be handle with multi developer in same team.. power apps yes, that is upcoming feature but in dataverse i have a little confuse. @cavitha

Was this reply helpful? Yes No
hazer_kirbasogl 9 on at

Like (0)

Report
Copy link

Link copied!

Actually, Im not fully mentioning Powerapps, i mean a little bit about solution deployment. How we can be handle with multi developer in same team.. power apps yes, that is upcoming feature but in dataverse i have a little confuse. @cavitha

Was this reply helpful? Yes No
eleung83 232 on at

Like (1)

Report
Copy link

Link copied!

The simple short answer is there is no easy way to try and merge customisations from 2 different environments into one single environment. This is especially the case if you are using unmanaged solutions when deploying between environments

I wouldn't bother trying to merge the solution files from the separate dev environments as you would just spend lots of time just inspecting the differences and easily still miss things

Your other main issue with the separate developer environments is if/when your devs are making changes to the shared entities e.g. Account/Contact. If you're using unmanaged solutions you could inspect the solution xml files, but again you would be wasting lots of time manually reviewing xml files.

One long winded way I could think of with this setup (but you would need to enforce strict customisation rules) is to have one environment with all shared entities and their customisations, which gets exported to each developer environment, and then you export managed solutions from each developer environment, and then manually review conflicts in your common dev environment. You could then export unmanaged again from your common dev environment. You would have to deal with the pitfalls of solution layering in your common dev environment due to the managed solutions (which brings unfortunate additional headache)

Was this reply helpful? Yes No
hazer_kirbasogl 9 on at

Like (0)

Report
Copy link

Link copied!

@eleung83 Thanks for perfect reply it will be really helpful for understanding to me..
What is the correct or ideal solution deployment for multi developers team.. i got your last opinion but it looks really confusing for newbies in team..
what is your path ? Are you using one shared dev environment ? Thanks.

Was this reply helpful? Yes No
eleung83 232 on at

Like (0)

Report
Copy link

Link copied!

There isn't a single correct deployment strategy as there's various factors that drives development teams towards whatever works best for them (e.g. team structure, competency of development team working with D365, frequency of releases, managed vs unmanaged solution, requirements for developing proof of concepts etc).

But the usual route that internal development teams start off with is one single development environment and all team members communicate what areas they are changing (e.g. if they are changing a form, changing some webresource, workflow etc) and stick with using unmanaged solution customisations. Then, as your team progresses, you can gradually see what kinds of patterns they use to get their work done, and from there you may want to introduce other environments and more structured solutions where you can then build out more ALM strategies.

Guaranteed you won't get it perfect from the start, but you'll have less headache to deal with at the start if you have one single dev environment and lay the responsibility on the developers to communicate with each other on what areas they are changing. And from there you can improve on it based on how your teams works

Was this reply helpful? Yes No