Error when importing a solution with custom connector

[Simon_Berg]

Hi

I got a solution with 5 tables and 1 cloudflow, 1 custom connector and 1 custom connector reference since i use the custom connector in my cloud flow.

When importing it to another environment as an unmanaged solution it fails when it asks me to create a new connection in my new environment.

Anyone got any hints on what to do?

[Anonymous]

Not ideal but with the amount of connectors at play, I would be tempted to drop them from the app. Then do the export/import and re-add. In my personal experience you will no doubt, in particular when it comes to Flows have to reconnect them anyway on the other side to avoid issues, so if it is causing you grief at the export/import stage, then not much difference in dropping the connection beforehand.

Although thinking out loud, you would probably not want to drop if in say a Live environment, in that case it may seem overkill but should work. That would be to export/import to a new instance within the same environment and then drop the connections from the duplicate instance for the purpose of importing and exporting.

Another way to go would be to make available say the customer connectors in the destination environment and have them available to select at the time of import.

Do you know which element that id equates to. Look to Source code files for Canvas apps | Microsoft Power Apps as that is something that can be useful to determine what relates to that Id if you are unsure. It also helps when you try and export/import and it complains because a Flow is being referenced in the app that no longer exists. You can gut it out, repackage and you are good to go.

[swe1]

Guess that's a known issue 😞
https://docs.microsoft.com/en-us/connectors/custom-connectors/customconnectorssolutions#known-limita...

• Custom connectors need to be imported first, before connection references or flows
  • If your environment doesn’t contain the custom connector in a solution, import a separate solution that only the custom connectors. Do this importation before you import the actual solution because Azure needs to register the custom connector beforehand.
  • If you import a solution that contains custom connectors and flows or connection references for the customer connector that was not previously imported in a separate solution, Azure will not be able to register the custom connector while it's registering your connection references or flows. If Azure hasn't registered your custom connector, the importation will fail, or you will not be able to start the import at all.

[Thoman]

So I created a new solution for my custom connectors. Imported the existing custom connector to my new Custom Connector Solution. I then Exported it as an unmanaged solution. I was then able to import it in the new development environment I created. 

Should my "Project Solution" also contain the custom connectors? When I try and import the solution into the dev environment I still get the same error.

[Thoman]

Update: I finally got it to import. I had to make sure my Custom Connector Solution was published in the new Environment and then also re-export the existing "Project Solution" that was using the connector after created the Custom Connector solution. At the same time, I had to update all my existing workflows that was using the old connector to the one created inside the solution. Very clunky migration but finally there.

TIP..... START ALL Power Projects as a solution! Don't "Migrate" them later. Else you will have to redo most of your work.

[russoedu]

Thanks a lot for this! It's absurd the amount of workaround we need to do to do simple things like "copying a flow inside solution", and migrating a custom connector to another environment.

I'm glad this community always find creative ways to "fix" the broken stuff on Power Platform.