Announcements
From what I am reading, there is no way to version control down to the Entity/table level.
D365/Powerapps technologies have been created with no way to version control down to the table component level?
Is that a correct statement?
Correct for Dynamics 365 / CDS / Dataverse tables etc. Any code .Net, JavaScript, JSON (if canvas app) you manage by putting in Dev Ops etc
For the data structure, one way to help manage is you create all your changes inside Solution Files and export these with an appropriate version number. (but note, the reimport is an upsert so you would roll it into a clean environment if you needed to revert.) Or you use the restore of the backups being performed continuously by Microsoft (but watch out for the retention periods). You can also use XrmToolBox (doc gen plugin) to extract a data dictionary to word/excel if all you need is details of what was there at a point in time.
Hi @urklnme ,
A good article to se the details that are available with ALM with Power Apps is the following: https://docs.microsoft.com/en-us/power-platform/admin/wp-application-lifecycle-management
Overall the Solutions in Power Apps is "good" but nothing like what you can do with true application development ALM tools with branching / tagging / etc.
Managed solutions will provide the ability to layer solutions and build upon capabilities of each and it will allow you to add patches and versions. If you remove a version of a managed solution it will remove the changes that you applied with that version so "it is a start" :).
Hopefully this information provides a good start. For a detailed ALM document around Power Apps / Dynamics 365, please see the following: https://docs.microsoft.com/en-us/power-platform/alm/
Hope this helps!
Thanks,
Drew
Hi @urklnme,
I would say that's false. To version control your configurations/customizations (e.g. tables) and code (e.g. plugins, JS) are done via your favorite source control. The platform SDK provide tools to pull down (aka unpack) the configurations/customizations into XML files which you can then manage in source control. Have a look at the links @dpoggemann provided, they're a quick read and provide all the details to have a healthy ALM. Specially for versioning/unpack look into:
Wow. Thank you all!!
One of my quandaries was that I had not found a good example of the artifacts created by the UNPACK.
Danilo Capuano provides a great explanation here: (with screen shots)
https://capuanodanilo.com/2020/11/30/alm-in-power-platform-using-devops-power-platform-build-tools-and-team-foundation-version-control-part-3-of-3-move-solution-from-qua-to-prod-and-check-in-unpacked-solution-and-zip-solution/
and it turns out that the Power platform build tools extension is already installed in my Azure organization.
On to the build tools!! 🙂
The community really does need a way to split the credit for great answers. What do I do flip a coin? one potato, two potato? 😄
Eric is much smarter than I am, give it to him! 😀
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
11manish 530
WarrenBelz 459 Most Valuable Professional
Haque 314
