Changing a Connection Reference in a Managed Solution?

(1) Share

Report

Posted on by rb

835 Super User 2024 Season 1

Hello,

We have two SQL Connections in our environment:

SQL-1

SQL-2

A Connection Reference in a managed solution was set up during import to reference 'SQL-1'.

Can we now edit/change/reimport this Connection Reference in our solution to point to 'SQL-2' instead?

Thanks in advance

Categories:

Using connectors

I have the same question (0)

All responses (13)

Answers (1)

DamoBird365 8,942 Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @metsshan

Are you referring to the following:

In which case, select add new connection for the first SQL action and then subsequently update all of the other Actions in the Flow.

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Cheers,
Damien

P.S. take a look at my new blog here

Was this reply helpful? Yes No
DamoBird365 8,942 Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @metsshan

How are you getting on?

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Cheers,
Damien

P.S. take a look at my new blog here

Was this reply helpful? Yes No
rb 835 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hey,

Thanks for checking in!

I forgot about this for a while because we have a bit of a workaround - but we still have the wrong connection assigned to a Connection Reference in a Production Managed Solution.

Because the connection reference is used by both Flows and PowerApps, I would like to change it here:
Obviously in an unmanaged solution I can Edit this connection reference. However, as a Managed solution we were able to assign the Connection to the Connection Reference during our first import, but do not know any mechanisms to change this ongoing.

FWIW I believe this should an available feature, especially as organisation may mature to towards more modern authentication types, segregation of duties etc - in which cases the need for new Connections may be required (not just editing existing ones linked to Connection References).

Thanks for helping!

Was this reply helpful? Yes No
kierian Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

In managed solution all components are in read only you cant edit or add new connection.

Was this reply helpful? Yes No
rb 835 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hey Kierian,

Thanks for that - so in my case, what are the options for getting the Connection Reference changed from SQL 1 to SQL 2?

It seems the only way would be to delete the Solution, re-import, and choose SQL 2 for the Connection Reference value. But then I would lose all the permissions to my PowerApp, right? Possibly worse - the App ID/URL could change?

Was this reply helpful? Yes No
kierian Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

You have to change connection on un managed solution once you did all change export it as managed solution that only way

Have a good day.

Was this reply helpful? Yes No
rb 835 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Sorry, but how would this work?

If I change the connection in the source environment, how does Power Platform know which Connection to use for the Connection Reference in the target environment after export? The connections will have different names/IDs/values....

Was this reply helpful? Yes No
Verified answer

rb 835 Super User 2024 Season 1 on at

Like (25)

Report
Copy link

Link copied!

In case anyone ever finds this, here is how you can change the Connection property of a Connection Reference in a Managed Solution:

Go to Solutions -> find "Default Solution" -> Find your connection reference and edit it's properties from here.

I hope this helps someone!

Was this reply helpful? Yes No
Hppyclown 23 on at

Like (1)

Report
Copy link

Link copied!

Legend!

Was this reply helpful? Yes No
RPraschma 9 on at

Like (0)

Report
Copy link

Link copied!

Nice.
Now finally a proper way to do this.
Thank you, thank you, thank you.

Didn't know about it.
The workaround I found was changing the connection ID in the connection reference table in dataverse using a cloud flow.
Super backend without knowing the full impact, but after turning the affected flows off and on again it actually worked 🙂

Was this reply helpful? Yes No