tag:blogger.com,1999:blog-7679200490261166601.post3223713895962878248..comments2024-03-01T00:18:45.839-05:00Comments on Mitul Suthar's Coding Blog: PowerApps From A DevOps PerspectiveMitul Sutharhttp://www.blogger.com/profile/10382570646381807553noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-7679200490261166601.post-21857698402131066262019-09-08T17:00:20.693-04:002019-09-08T17:00:20.693-04:00Great Points, Mitul.
Last year I was working on a...Great Points, Mitul.<br /><br />Last year I was working on a large PowerApps application with a colleague. We were able to somehow split work between two of us. For example. I would do MS Flow development that would drive the PowerApps while my colleague would do the PowerApps. Sometimes we would develop different screens and then, at the end of the day just "merge" everything by copy-pasting. Developments to QA, UAT and PROD was super-fun as well: We wrote a 100-page deployment guide with screenshot and all. <br /><br />We also realized that you can modify the exported .ZIP PowerApp/Flow. It's just a bunch of JSON files. I doubt it is supported to meddle with the source code, but we still did it to easy our pain of moving the apps from one environment to another. Here is an example of a script we wrote: https://github.com/Zerg00s/FlowPowerAppsMigratorhttps://mscodingblog.blogspot.com/logout?d=https://www.blogger.com/logout-redirect.g?blogID%3D7679200490261166601%26postID%3D3223713895962878248Denis Molodtsovhttps://www.blogger.com/profile/08493433394183206907noreply@blogger.comtag:blogger.com,1999:blog-7679200490261166601.post-25862190108788777952019-05-06T11:43:48.911-04:002019-05-06T11:43:48.911-04:00Best explanation ever!!Best explanation ever!!Israelcrhttps://www.blogger.com/profile/02145492154017229254noreply@blogger.comtag:blogger.com,1999:blog-7679200490261166601.post-523326285948309572019-02-18T11:50:44.840-05:002019-02-18T11:50:44.840-05:00Thanks for sharing, very useful info.Thanks for sharing, very useful info.Anonymousnoreply@blogger.com