Skip to main content

Notifications

Power Automate - General Discussion
Suggested answer

Import solutions with custom connectors

Posted on 28 Nov 2024 12:25:18 by 13
Hi,
 
I am new in power automate, and the power platform in general, so I started creating all my flows within the default environment. I have now realized my mistake and have created a test, dev and prod environment.

I then tried to import my different flows, packaged as solutions, into my newly created dev environment. A lot of the solutions transfered without any problems, except one of them. This solutions only differance is that it contains a custom connector.
 
Whenever I try to import the solution I'm met with this error(see attached picture). I have no idea how to fix this. I have searched around a lot, and some places it seems like you have to create the custom connector on each new environment, but this still didn't work. 
 
So I'm finally turning here, hoping someone knows the anwser to my problem :)
 
Thanks,
Mikkel
 
 
Categories:
  • MH-05110755-0 Profile Picture
    MH-05110755-0 13 on 28 Nov 2024 at 13:46:15
    Import solutions with custom connectors
    Hmm. I tried what you suggested. Both just importing the custom connector directly in solutions, from already existing, and also as a solution on it's own with just the custom connector inside, no references or anything else.
     
    It still gives me the same error when I try to import the original solution. I tried redownloading the solution to see if that helped, but no dice. Do I need to remove anything from the original solution before importing? Refernces, connectors, flows?
     
     
  • Suggested answer
    CFernandes Profile Picture
    CFernandes 8,000 on 28 Nov 2024 at 12:37:59
    Import solutions with custom connectors

    When importing a solution that contains a connection reference of the new custom connector into a new environment, the import process asks for a connection to be created for the connection reference. But because the connector doesn’t exist in the new environment, the connection can’t be created.

     

    A workaround is to put the custom connector in its own solution and then first import that to the destination environment.

     

    This is documented under the known limitations of the custom connector.


     

    Custom connectors need to be imported first, before connection references or flows.
    If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
     
    P.S. take a look at my blog here and like & subscribe to my YouTube Channel thanks.

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

November 2024 Newsletter…

November 2024 Community Newsletter…

Community Update Oct 28…

Power Platform Community Update…

Tuesday Tip #7 Community Profile Tips…

Welcome to a brand new series, Tuesday Tips…

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 143,151

#2
RandyHayes Profile Picture

RandyHayes 76,308

#3
Pstork1 Profile Picture

Pstork1 63,845

Leaderboard

Featured topics