You’re offline. This is a read only version of the page.
2
Hi, this article hints the mentioned subject: https://docs.microsoft.com/en-us/powerapps/maker/data-platform/create-connection-reference. But can anyone confirm it ? It seems that connections references for now are just not possible when using a sharepoint connection within the context of a Canvas App in a solution because connection reference usage from a Canvas app is only supported for non-Oauth based connections (which excludes the SharePoint connection). When using the power automate flow sharepoint connection combo, it however should be possible. However, in any case the needed SharePoint connection within the clean target environment would still not be created automatically and has to be created manually the first time the environment is targeted by the deployment pipeline, as mentioned in this post: https://www.develop1.net/public/post/2021/04/01/connection-references-with-alm-mind-the-gap. This limitation really frustrates the DevOps principle of automating everything you can and achieving continous delivery. It would be great to know if anyone else has encountered this limitation and has any ideas on how to handle it ? Ideally it would be great to know if and when the power platform team will close this ALM gap...
So what is the piece bothering you here? The fact that when you move to a new environment you need to fix the connection reference?
That is deliberate, because it is assumed that your connection reference in Dev is not the same as your connection references in QA, Prod, etc.
Once you set the connection reference in the target environment the first time, it should import again and again cleanly without manual intervention. so this does not present a problem for ALM, just a single manual step that has to be done the first time you go to a new target.
Share
Report
All responses (
Answers (
