I wonder if you could go into some tips when deploying an UPDATED managed solution over an OLDER managed solution where connections were previously used. Let's say, DEV to QA environment. Obviously some unmanaged layers would have been previously created in QA. Does one have to completely uninstall the managed solution in QA before deploying the updated one? Do managed layers need to be deleted for each flow manually?
Is there a way to update existing flows, added to a solution, but not created within one initially, to use connection references instead of connections?
When did you create this flow? If you created it before November 2020, the feature wasn't out yet.. If that was the case you need to export the solution and then import the solution that will create the references.
But this still doesn't solve the problem that when different SharePoint sites are setup to work in different environments (DEV, UAT, PROD...etc). Very often in DEV environment we develop Power Apps or Flows with a DEV SharePoint site. When the solution is migrated to UAT, we still need to update the the app or flow to point to the UAT SharePoint site, and then do the same when deploy to PROD. Anyway around this, please?
The video you want check out is the one on Environment Variables which allows you to plug in 'tokens' into your configuration like SharePoint sites. Connection Reference help with connections, not the configuration within your flow. ua-cam.com/video/gTcDcOH3V0E/v-deo.html
Thank you
I wonder if you could go into some tips when deploying an UPDATED managed solution over an OLDER managed solution where connections were previously used. Let's say, DEV to QA environment. Obviously some unmanaged layers would have been previously created in QA. Does one have to completely uninstall the managed solution in QA before deploying the updated one? Do managed layers need to be deleted for each flow manually?
Hi Kent, great demo. too bad connection references cannot be configured with Power Platform Build Tools in Azure DevOps
Thanks - not yet :-)
Is there a way to update existing flows, added to a solution, but not created within one initially, to use connection references instead of connections?
Yes - I covered it in my latest video here: ua-cam.com/video/Hf2_0MQ9Pfg/v-deo.html
I'm sorry i don't see the Connection Reference feature. is it already disabled?
When did you create this flow? If you created it before November 2020, the feature wasn't out yet.. If that was the case you need to export the solution and then import the solution that will create the references.
Thanks a lot for this great demo
Glad you liked it! Thanks!
But this still doesn't solve the problem that when different SharePoint sites are setup to work in different environments (DEV, UAT, PROD...etc).
Very often in DEV environment we develop Power Apps or Flows with a DEV SharePoint site. When the solution is migrated to UAT, we still need to update the the app or flow to point to the UAT SharePoint site, and then do the same when deploy to PROD.
Anyway around this, please?
The video you want check out is the one on Environment Variables which allows you to plug in 'tokens' into your configuration like SharePoint sites. Connection Reference help with connections, not the configuration within your flow. ua-cam.com/video/gTcDcOH3V0E/v-deo.html