Power Platform Community Forum Thread Details

Hey, we are trying to create a solution which can we import to different environment. for this i am trying to add the custom connector i have created outside of the solution and then i am trying now to add this to the solution so that i can parametrize the host name settings in the custom connector. but it is taking too long without any error, and not getting added. Is this expected?

how can do this process, below are the screenshots if this helps:

Categories:

Connector development

Hi @PM-15011420-0,

This is a known issue with the Power Platform "Modern" interface. When you create a custom connector globally (outside a solution) and try to "Add existing" to a solution, the process often hangs indefinitely or times out, especially if the connector has specific sharing permissions or if the definition is complex.

Here is how to solve this, ordered from the easiest fix to the most robust long-term solution.

Solution 1: The "Unshare" Trick (Quickest Fix)

The hanging behavior is often caused by conflicting permissions.

Go to Custom Connectors (outside the solution).
Select your connector and click Share.
Remove all other users or security groups so you are the sole owner.
Go back to your Solution and try to Add existing > Automation > Custom Connector again.
If successful, you can re-share it after it is added.

Unable to add custom connector to a solution Not a verified one But you can refer it.

Solution 2: Create "Solution-Aware" from Scratch (Recommended)

Since your goal is to parametrize the Host Name (using Environment Variables), you strongly benefit from creating the connector inside the solution natively rather than adding a legacy one.

Open your Custom Connector in a separate tab and download its Swagger/OpenAPI definition (or copy the YAML/JSON).
Go to your Solution.
Click New > Automation > Custom Connector.
Select Import an OpenAPI file and upload the file you saved in step 1.
Crucial Step for ALM: When configuring the connector inside the solution, you will now see options to bind the Host URL directly to an Environment Variable.

This is much cleaner than trying to patch a legacy connector later.

Solution 3: Use the Classic Interface (Fallback)

If you must add that specific existing connector and Solution 1 failed:

In the URL of your Power Apps environment, look for forceUCI=1 and change it to forceUCI=0 or try to access the Classic Solution Explorer via "Switch to Classic" (if still available in your region's settings).
Try adding the component from the classic view. The old interface often throws a visible error instead of hanging, which can tell you why it's failing (e.g., a policy violation).

Hope this helps!