Answered

Moving changes to another environment

(0) Share

Report

Posted on by tedqn77

127

I have a solution on dev instance with one model driven and a couple of canvas apps. The canvas apps access the dev Azure MS SQL database, same tables. Upon export/import for the first time into staging, it asks to re-create the db connection to the sql server. Then it said I have to go into the app to re-reference the sql server tables that the app needs to access. The problem is I updated the connection for canvas app 2 first, and the new table reference gets the name "table1". On dev it gets "table1_1" (since canvas app 1 was set up first and got "table1"). So now both apps code referencing the wrong table names. I had to manually edit each app's code to reference the correct tables to get them to work.

After that, I re-imported the same solution thinking it will revert the code back to original and the apps will break again. But it didn't change the modified code on staging. So my questions are:

1) what happens if I make future change to the code on dev and release? Will it update the code on staging?

2) I've noticed in the solution view for staging I cannot change app's code (managed), but when going outside of the solution in the all apps list, I can modify the code. What will happen on the next release?

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (1)

jatcube 508 on at

Like (0)

Report

@tedqn77 the built-in export/import function can be a bit of a hit and miss at times.. but any future changes should apply just fine. However, it seems there's a bug around caching connections (references) in powerapps and sometimes they don't get updated or new connections added. If that happens to you, just delete the managed solution altogether and reimport it.

2. that has to do with allowing customizations. You can turn that off under Advanced -> Managed Properties. in a nutshell, you can allow customizations even in managed solutions, so you can decide which are the core parts of your solution that absolutely must never be changed and which you may want to allow users to change so you don't have to make all the changes yourself for many different environments.

For more info: https://docs.microsoft.com/en-us/power-platform/alm/managed-properties-alm

Was this reply helpful? Yes No
tedqn77 127 on at

Like (0)

Report

Thank you. I discovered that I can manually delete the referenced table names and re-select, it will re-create with the same names as in ms sql database now, for both canvas apps instead of going "table1" then "table1_1".

As for the modification on staging, you're saying that if I modify a label or code there, the next release from dev will overwrite it with the label, code from dev?
What if I add a new choice item (in dropdown list) in staging and dev doesn't have it? will it delete the new choice item or preserve? I think that would be data, not structure so it won't be touched.

Was this reply helpful? Yes No
Verified answer

jatcube 508 on at

Like (0)

Report

@tedqn77 you have 3 options when importing a solution that already exists in the environment: upgrade, stage for upgrade and update.

Upgrade is the recommended (and default), it will remove components that are no longer present in your solution (because they were deleted in dev) and adds any new ones.

You can read more about the rest here https://docs.microsoft.com/en-us/power-apps/maker/data-platform/update-solutions

You do however need to make sure that all components are added to your solution. This usually happens automatically, but sometimes you need to use the add existing option (especially if they were created previously) so they are included in the solution on export and hence import. This includes everything, such as tables, choices, flows, etc.

If you found this response useful, give it a thumbs up and don’t forget to mark your post answered to help others find the solution easier.

Was this reply helpful? Yes No