Skip to main content

Notifications

Community site session details

Community site session details

Session Id : 3XyX3K4z/TrrottyNITLNy
Power Apps - Power Apps Governance and Administ...
Answered

Are connection references Solution Dependant

Like (0) ShareShare
ReportReport
Posted on 6 Feb 2025 15:06:32 by 111
Hi All - I have a unmanaged solution where there are flows, apps and environment variables. My flow uses connection references. I have a connection reference ABC which is being used.
 
Now i created another unmanaged solution which has flows and apps. I did not notice but in this new unmanaged solution my flow was using connection reference ABC of the other solution. I was able to export and import this unmanaged solution to managed solution in another environment without any missing dependencies warning.
 
Now all of a sudden today when exporting this solution i get a warning which contains a list of missing dependency and in that there is connection reference ABC as well.
 
Now my question is how does this work. Can we reuse connection references between solutions? Why was my 2nd solution working for so many days without connection reference ABC inside it and all of sudden today it shows me this missing dependency. Also to note the application is live in production and the flow using this connection reference also works well in prod.
  • ST-24070323-0 Profile Picture
    111 on 10 Feb 2025 at 05:24:04
    Are connection references Solution Dependant
    @FLMike - So the dependency warning comes when exporting the solution. Which had never arose before. The strange part is that connection reference is used by two flows within that solution. However the dependency warning is shown only for one flow. Why is it not showing for the second flow?
  • Verified answer
    Michael E. Gernaey Profile Picture
    35,752 Super User 2025 Season 1 on 06 Feb 2025 at 16:09:52
    Are connection references Solution Dependant
    Hi,
     
    So you should never "not" add. Flows are a different beast because technically you add them to the solution, but if you go to put it into an environment that already has the dependencies you wont see errors.
     
    So for you to get that error, it tells me something changed in the solution that had the flow and was being exported and imported.
     
    So to me the missing dependency tells me the original flow connection reference etc changed. You haven't shared any of that and most people just say  oh nothing changed (and its usually not true).
     
    So don't look for things by name. Look at the dependency it says is missing and use the GUID to determine if it really exists any more.
     
    If someone redid it (For any reason), in the original solution then this solution will fail, as expected.
     
    Share some photos of the errors, the flow, the ID of the connection references etc etc
     
    P.S. you should always remember to add the connection references to all solutions, even though, technically you can get lucky like this and it will work simply because the flow already existed IN the environment prior to this now broken solution installed.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Thomas Rice – Community Spotlight

We are honored to recognize Thomas Rice as our March 2025 Community…

Kudos to the February Top 10 Community Stars!

Thanks for all your good work in the Community

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 146,508 Most Valuable Professional

#2
RandyHayes Profile Picture

RandyHayes 76,287 Super User 2024 Season 1

#3
Pstork1 Profile Picture

Pstork1 65,369 Most Valuable Professional

Leaderboard

Featured topics

Loading started
Loading complete