Unable to edit Custom Connector

[ev_enter]

I am the owner of the connector.

It was working fine and didn't make any changes to it only created connections to it and used its actions in a flow.

Click on Edit in the list of connectors, but none of the fields are editable, and the "Update Connector" action is missing.

Can click on Swagger editor, but nothing there is editable either.

The other connectors are editable, and ideally don't want to create a new one because it is used quite extensively in a flow.

Only saw this after publishing the solution via pipelines to the production environment. Where after publishing I need to change some of the settings that do not copy over during deployment.

Back in the development environment, I suddenly can't edit the Connector there either.

Tried removing the items from the solution.

Removed the solutions.

Tried different browsers.

Tried different machines.

Tried different browsers on different machines.

[vidhy]

Same issue from today 31 Jan. Is there any update / change regarding how to update connector as it opens always in view mode once created

[julian_castro]

I'm having the exact same issue today 31 Jan.

[KonstantinFuksz]

I have the same issue on my environment and also confirmed at the customer's environment. However, after playing with CSS inside html I made it work somehow. Tried to reproduce the same actions on the customer's environment - it did not work.

[zolle04]

same to me. Not able to edit Custom Connector in Dev Env

[yasmany]

It was happening to me as well, seems to be working now.

[ThomasMDP]

Any updates on fixing this? Or does it just randomly start working again?

Edit: I am able to edit other custom connectors, just not the one that needs editing right now.

[zolle04]

my current workaround:

Create a new connector -> new page opens -> no further action required

Go back to overview of custom connectors

-> Editing is now possible

[Johanlb]

Same here. Workarounds given earlier by members don’t work for me. 

[zolle04]

does my woraround work?

[ev_enter]

Unfortunately, not.

[lodhavin]

Thank you for sharing your experience. We have encountered a similar issue, but it seems to occur specifically when the custom connector is included as part of the solution (In our case). It's interesting to note that the behavior is consistent across different environments. Let's keep each other updated on any progress or insights we gain regarding this issue.

[friendbool]

I have the same problem too.
The only solution I found is to update the connector using paconn.exe at this link the procedure. https://learn.microsoft.com/en-us/connectors/custom-connectors/paconn-cli
Does anyone have any other solutions?

[Maxxim]

Please for the love of God, someone find a workaround as soon as possible!

[Johanlb]

I have opened a ticket as critical to the support. 

[_powerDeveloper]

Also here starting from 31 January as well. I created an account only for this.

[mki1]

I'm experiencing the same issue (noticed today Feb 1) for two (out of two) custom connectors in the same dev environment. Cannot interact with anything on the screen within the selected setting (General/Security/Definition/etc.). In addition, the Description field for the majority of the actions in one of the connectors seem to have been cleared (I really hope this does not count for any of the Request or Response configurations...).

Does anyone know if it is possible to find the ticket that @Johanlb created and somehow add that you are experiencing the same issue?

[deepakMehta]

Hi All,

I am still facing the same issue.  Not able find any solution of it.

[AlexTofan]

Run this PowerShell script:

Set-AdminPowerAppConnectorRoleAssignment -ConnectorName <connectorname> -EnvironmentName <environmentname> -RoleName CanEdit -PrincipalType User -PrincipalObjectId <principal objectId>

Or use the Power Apps for Admins  connector's Edit Connector Role Assignment as Admin action
Power Apps for Admins - Connectors | Microsoft Learn

You can get the environment name and connector name from the custom connector's URL:

https://make.powerautomate.com/environments/074fc71e-042e-4297-a8ca-288f2734c2f2/connections/available/custom/shared_gdsc-5fgdsc-6u4jfioi42457823/details

The principal object ID is the connector owner/editor's Azure Active Directory ID that you can get from https://portal.azure.com >> search for the user >> copy the user's object ID.

Looks like this issue is happening because custom connectors in solutions do not have role assignments in BAP. BAP is the initial Business Applications Platform and custom connectors are BAP objects, not Dataverse objects. When Dataverse started to support custom connectors in solutions, custom connectors basically merged with Dataverse, in the sense that they got their own table "connector". This table stores the custom connectors that are created in solutions.

With this bug, Microsoft managed to break the relationship between BAP and custom connectors, in other words, because solution-aware custom connectors do not have role assignments in BAP, now the connector "studio" is no longer recognizing you as a connector editor/owner and is not honoring the Dataverse role assignments either. This is because you did not have a role in the first place in BAP (hence why custom connectors in solutions can't be retrieved via API unless it's got BAP roles). The solution is to create a role assignment in BAP using one of the methods mentioned above.

[austinm34]

I ran this command using the Power Shell tools for Power Platform, but I get the error with code NotFound.