cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Collaborative development in Dataverse

Is there a recommended approach for multiple users working on a model driven app? More specifically, is there any way to know if someone else is modifying the same dataverse table form that you are working on, within the same solution? Is there a workflow where developers can collaborate through the creation of individual / feature based solutions (similar to a feature or defect fix branch in a code repository) , that can then be merged into a shared solution?

Thank you!

10 REPLIES 10
Devvj
Super User
Super User

Hi @akatakkar 

There are tools like the ALM Accelerator which have some advanced features around branching and ALM in general, it is fairly powerful if utilized correctly, but it is pretty advanced.

Anyway, if you want to take a look there is some information on the branching part here:
Branching and environment strategy - Power Platform | Microsoft Learn

 

Hope that helps!

-------------------------------------------------------------------------
If this answer for your question, please mark the post as Solved and leave a Like.
Find me at LinkedIn
EricRegnier
Most Valuable Professional
Most Valuable Professional

Hi @akatakkar,

There's not an approach that fits all, but there's definitely some guidelines and best practices. I'm working in large scale implementation in teams of over 40 developers working on the same Dataverse instance and model-driven apps so the platform can definitively support it and has been enterprise scale for a while. Suggest taking the time to go through the official ALM documentation: https://learn.microsoft.com/power-platform/alm and get familiar with some the concepts:

  • Environment strategy
  • Solutions and solution layers
  • Source control and unpacking solution - the best approach is to follow the principle that your source control is the source of truth for your configurations (e.g. tables) and customizations (e.g. JavaScript and code).

 In short, the overall process is:

  1. Developers perform their changes in their own developer environment (env) or sometimes in a shared dev env. They create their dev from a clone or sometimes install a solution version from git (#4 below) into a vanilla env.
  2. They create a feature branch off of main/master and once ready to commit/deploy, they unpack the solution from their env. We use the sync command from the pac cmdlets to unpack which makes life easier.  They then review and commit their changes to the feature branch and submit a PR to main.
  3. When main is updated, a pipeline triggers to generate the solution off of the main branch. We use the pack task from the ADO Power Platform build tools.
  4. Solution is now a build artifact and deployed to the target environments, using the ADO Power Platform build tools.

There's lots more happening within these steps, but that's the gist of it.

Hope this helps a little!

Echo everything @EricRegnier says there. The platform absolutely supports enterprise scale development; I've run teams of similar scale myself.

 

The question is not whether the platform can do it, but whether your practices can. No matter the platform and no matter the ALM strategy, if you have devs failing to coordinate and fighting each other's work, the whole machine will grind to a halt.

ChrisPiasecki
Most Valuable Professional
Most Valuable Professional

I'm going to go against the grain here and push back against @EricRegnier and @cchannon's comments.

 

ALM is one of the most difficult parts and pain points of the platform when large team or parallel team development is involved.

 

Unless your team is very disciplined and avoids working on the same components, and syncs developer environments after every PR, be prepared to spend a lot of time dealing with solution merging conflicts. This is especially true when you have separate developer instances and are working with existing components. If you work in a single shared environment, you will spend a lot of time bringing over unfinished features to a build environment to clean them out manually and removing dependencies (unless you decide to try and follow a, feature flag development approach) . If you're touching the same components, expect forms, views, ribbon customizations, entity metadata, model driven apps, and other components to get overwritten by each others changes. 

 

Another issue is the unpacked components are mostly XML, which isn't very git friendly and sometimes the git algorithm does not always automatically merge the way you expect, so manual intervention is involved.

 

Then there are some things that are either not solution aware, or require custom scripts to automate deployment, or can't be automated at all.

 

Personally I find ALM in the Power Platform much more difficult than custom development because of all these complexities and many areas being a black box, and a lack of auditing when it comes to customizations being made, so you can't tell who made what changes in a shared environment. 

 

Things I can suggest are:

  •  creating small topic/feature solutions that only contain compoments you are changing. Then transport them to a master dev environment to merge and remove unnecessary components/dependencies where applicable. 
  • Sync all development environments often to reduce the risk of stale components overwriting newer changes and causing regressions. 
  • Avoid working on the same components at the same time, especially forms and views. 

 

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.
Chris

Thank you Devvj. I'm reading through the information. Because we have so little code (i.e. a Model driven application), I needed to better understand how to use solutions to created isolated development environments for each developer. Previous to this, I have always worked with code and branching strategies, so this concept of 'low code applications' is all very new to me. Setting up development environments, like in the following link, seems like a step in the right direction: Sandbox environments - Power Platform | Microsoft Learn . I'm also going to check out the ALM accelerator. Thanks for pointing me in the right direction. 

Hi Eric,

Thank you for your response. I will definitely read through the ALM documentation. Also, thanks for letting me know that solutions can be maintained in GIT. I'm familiar with git branching and merging so am very comfortable with the concept of creating feature branches and then merging back into a main branch. The gist is all I need for now - many thanks for giving me hope.

Hi CChannon,

Thank you for your response. I totally agree that our devs will need to be on board with whatever approach we take and coordinate with each other. I will read up on the docs. 

Hi Chris,

I really appreciate your response. Though I am used to dealing with merge conflicts, I am unaware of the subtleties of merging things like solutions. We currently don't even have independent development environments, so if we implement your 3 suggestions, it will be an improvement. This gets me 1 step closer to making some informed recommendations. Thank you.

@ChrisPiasecki, we really have to do a session and discuss the pros/cons and pain points of ALM approaches 😉

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (1,227)