Answered

Power Apps Solutions Importing Bing Maps connector issue

(0) Share

Report

Posted on by taron_wright

I have imported an unmanaged solution into a developer environment. When I import the app I get the choose to choose all new environmental variables for my data sources which is great. I then also get the choice of creating connections for my connection references in the environment which is fine. However, when I go to use the app I get this error with Bing Maps connector:

My app has this connection already inside of it. However, there does not seem to be any way to get the Bing Maps connector to use my connection reference that I created in the environment. I believe it may just be using the standard connection. I can solve this with some work around which involves going into the app and deleting the connection. However, this is not a viable solution as when I want to deploy this into a production environment as a managed package, I won't have the ability to edit anything.

Also, what is that "Connection by Microsoft" and why is it locked?

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Anchov 1,986 on at

Like
a
(0)

Report
Copy link

Link copied!

One approach to try is accessing your solution, locating the app, and right-clicking to add required objects. Check to see if another Bing connection reference is added, possibly outside of the solution. Then delete the Bing connection reference that is not being used.

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Cheers!
Rick Hurt

Was this reply helpful? Yes No
taron_wright on at

Like
a
(0)

Report
Copy link

Link copied!

@Anchov thanks for your reply.

Unfortunately this did not work. I clicked on "add required objects" and then selected "add". However, no new objects were added to my solution.

Was this reply helpful? Yes No
Anchov 1,986 on at

Like
a
(1)

Report
Copy link

Link copied!

In most cases, Power Apps does not create connection references for data connections (with few exceptions), because the data connections usually use the user's context. Its only when the app uses another context (like a service account), that a connection reference will added. In this case, I would remove the bing connection in the power apps, re-add it back, and republish. If the error goes away, then I would try exporting it and re-importing it out into another environment to see if the error comes back. If it does, sounds like there might be some type of corruption with the power app.

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Cheers!
Rick Hurt

Was this reply helpful? Yes No
Verified answer

taron_wright on at

Like
a
(1)

Report
Copy link

Link copied!

I followed your advice. I deleted the Bing Connection in the default environment. It was connected to so many different variations of the app and I believe I must have accidentally deleted the automatically created connection reference a while back. So when I was using my manually created connection reference, the power app was not picking up on it as it was looking for the automatically created one.
So when I deleted this connection and re-added it, I had to go into the app and also re-add the connection. I saved the app, re-published it. I then followed your previous advice and selected the "add required objects". The solution then created a new connection reference and viola, when I exported this solution and imported it into a fresh developer environment it worked perfectly. Thanks!

Was this reply helpful? Yes No