You’re offline. This is a read only version of the page.
22
Hi,
During import of a solution to our production environment, a timeout occurs when loading the "connections picker":
Any ideas what might be causing this?
I have tried the following:
I have also tried to import another solution, which is already running on production, on our preprod -> same timeout occurs. The other solution was imported on production a couple of weeks ago without any issues.
BR Morten
My workaround is to import through the classic interface. However through the classic interface, it doesn't give you the option to chose to verify the connection references and it doesn't let you set the environment variables. I had to go into the default solution to set that all up manually. Luckily for us, it seems that the import in the modern UI is back working again after not working for 2 days.
MAYBE NOT RESOLVED?
Good evening. I am still getting the very same error message (shown in the screenshot of the issue). Sometimes it happens before the "Review and adjust all connections" button shows up. Several retries later, I was able to click the "Review and adjust all connections" button but still got the same result. Same is happening to another team member of mine. I don't believe this issue is resolved. I've attached a screenshot taken early this afternoon after several failed attempts.
I agree that it is/was a bug. In my case the feature fixed the issue with importing the solution
However, afterwards I had to create a new ticket, because I couldn't allow my app to use the connection (I mentioned that in an earlier update to this case as well, after I tried to use the old UI for importing).
Yesterday I finally got through to a knowledgeable MS engineer, who told me, that the introduction of "secure implicit connections" earlier this year affected my app, because it was created prior to this update. So I had to deactivate "secure implicit connections" in the app, publish it and then import the solution to Production again. I just found this article, when I searched MS documentation https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/connections-list#shared-connections--secure-implicit-connections which explains it to some degree.
It's crazy that they release something, that breaks existing apps, without any kind of warning or notifcation on the app. And I have talked to 10+ MS supporters on this case, who apparently didn't know anything about this either...
I hope they'll find a solution for your problem as well.
Using a separate solution was just a side note. It's not necessary, but makes troubleshooting easier and best practice for reasons mentioned.
The toggle did nothing for me, which you mentioned. Same error. Maybe requires a patch to work.
Anyway, I just didn't want people to be misled about this being an issue with dependencies or layers which someone else mentioned. That was the main reason for my comment. This is a bug, and they need to fix it.
This is not about dependencies, solution layers, or that toggle "Review and Adjust all connections", which someone else mentioned. This is a bug with importing connection references and loading the connections. I have a ticket open with MS. To get around this I deployed the connection references via the legacy UI. Once the solution is deployed, you should be able to deploy through Power Apps if you need to deploy again.
It's also good practice to have your connection references in a separate solution and deployed first. Otherwise you will be prompted to create new connections when importing Power Automate Flows, which can be problematic, as it will create new connection references with different id's. In the past this created solution layers. I'm not sure if they've corrected that, but you should deploy your connection references separately first regardless.
Hi,
I have just asked MS support, and the toggle should automatically turn up, if the solution you try to import contains a match for an existing connection reference like in my case.
According to MS the feature was released in March as a part of a larger release to introduce "ability to adjust all connections". They shared these two dumps with me:
However, it didn't work on our environment until last week, so my best guess is, that the initial release contained a bug.
If you continue to experience this issue, I'll recommend you to create a support case like I did.
BR Morten
Stay up to date on forum activity by subscribing.
#1
stampcoin
84
#2
DS-11051211-0
20
#3
MS.Ragavendar
9
Share
Report
All responses (
Answers (
