web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Unanswered

Connection Reference not showing connections due to connector ID mismatch in managed solution

(0) ShareShare
ReportReport
Posted on by 13

Hi all,

 

We are running into an issue with connection references and custom connectors across environments, and would appreciate any guidance.

 

Context:

 

We are deploying a managed solution (Core Build) across environments (Dev → UAT → Prod) which includes:

 

  •  

    A custom connector: Stripe - Donations Connector


  •  

    A connection reference used by flows



  •  

Issue:

 

In one environment(PRD) , when trying to assign a connection to the connection reference, the dropdown shows no available connections, even though:

 

  •  

    The custom connector exists


  •  

    Multiple connections have been created successfully


  •  

    Connections are shared with users and service accounts



  •  
 

Investigation:

 

  •  

    In the Custom Connector → Test tab, connections are visible and usable


  •  

    However, in the connection reference screen, the Connector field appears blank or does not match


  •  

    It appears that the connection reference is pointing to a different connector ID than the actual connector in the environment


  •  

    The connector and connection reference were created at nearly the same time, which may have caused a mismatch


  •  
 

Comparison:

 

  •  

    In other environments (UAT ), this works correctly


  •  

    In those environments, the connector was created before the connection reference



  •  
 

Constraints:

 

  •  

    The solution is managed, so we cannot modify or recreate the connection reference

  •  

    We want to avoid creating unmanaged components or editing managed flows



  •  
 

Question:

 

Has anyone encountered a connector ID mismatch between a connection reference and a custom connector?

 

Is redeploying the solution the only supported fix?

 

Is there any way to rebind or repair the connection reference without recreating it?


     
 

Any help or confirmation would be greatly appreciated. Thanks!

image (5).png
I have the same question (0)

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
Pallavi Phade Profile Picture

Pallavi Phade 102 Super User 2026 Season 1

#2
11manish Profile Picture

11manish 73

#3
Abhilash Warrier Profile Picture

Abhilash Warrier 55 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans