Unanswered

GitHub Actions for Power Platform

(0) Share

Report

Posted on by jfeemster

When modifying an existing client application that has a large associated database using the GitHub Actions, the export to production needs to be done without changing any of the existing data in that client database. The GitHub Actions for Power Platform demo states that it is using "export/import solution" functionality, which would seem to include a database that would overwrite the production database. Hopefully this does not mean that the client database needs to be stored in GitHub along with the application. The demo is not clear on this issue.

Categories:

Application Lifecycle Management (ALM)

All responses (2)

Answers (0)

jd_feemster 2 on at

Like (0)

Report

Re: GitHub Actions for Power Platform

Thank you for the reply. It clearly was the preferred answer I hoped for. Unfortunately, development was done in the Default environment by previous users. Attempting now to move development to ALM using GitHub Actions, but have not found a way to move the data from Default to any other environment. Any suggestions?
Mikkelsen2000 on at

Like (0)

Report

Re: GitHub Actions for Power Platform

Thanks for reaching out and sorry if this isn't clear. Can you pls. share which demo you are referring to so we can rectify this? When we talk about exporting solutions, it is only the application/solution metadata, i.e. the definition of the app itself, not the data contained in the db. You can read more about solutions here: Solution concepts - Power Platform | Microsoft Docs