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.

[mackemlad]

Thanks for the suggestion.

Unfortunately, I ran that command and am still unable to edit the connector.

To be sure I had the correct parameters and the command worked, I ran:

Get-AdminPowerAppConnectorRoleAssignment

 ...and  received in response a list of all current connector role assignments in my environment.  There are only two - one for each of two users.

Before running the command, the entry for my user included the following:

RoleType             : CanViewWithShare

... and after the command it looks as follows:

RoleType             : CanEdit

 ...which leads me to conclude that the command did what was intended, yet even after navigating afresh to my list of connections and selecting the one I wish to edit, the edit option is not shown.

I have tried refreshing the page, clearing cache and logging out and back in again, but to no avail.  Do you have any other suggestions I could try?

[PV12]

Hi All, It seems we are passing the connector name wrongly, I did the above Get-AdminPowerAppConnectorRoleAssignment in powershell and I got all the connector details, it seems all the connectors prefixed with shared_connectorname-numbers-numbers("shared_testconnector-5f934disjd-5fsdnsjnd). When I passed this connector name in powershell or in Flow My issue got resolved. Make sure open the Powershell in admin mode.

In Flow

[austinm34]

I did try it this way by finding the full name of the connector like you described, however I had no luck. I just get an error that says "Not Found". Also, I used my user object ID as the principal object ID. is that correct?

[mackemlad]

@austinm34 - when I issue the

Get-AdminPowerAppConnectorRoleAssignment

I get a response similar to:

I used the value associated with the circled property (PrincipalObjectId).  I determined this to be the correct user from the value of PrincipalEmail.

[mackemlad]

[deleted]

[Johanlb]

Hi, 

For those who are not really confortable with Power Shell, like me and other Mac users, as explain earlier, you can use the Power Apps for Admin connector : 

Build a quick Button Flow (or even an App triggered Flow) with a single Action, namely: Power Apps for Admins - Connectors | Microsoft Learn (Standard Connector).

More explanation regarding the Input parameters for this Action.

• <connectorName>, you can find it in the URL within the Power Automate Maker Portal when you open the Custom Connector after ‘/custom’ and before ‘/edit’. 
• <environmentName>
• <roleName>, same as before, it should be: CanEdit
• <principalObjectID>, this should be the User Object ID for the user that needs to edit the Custom Connector. Also named Azure Object ID.
• <apiVersion>, it’s already populated by default with the value 2017-06-01.
• <fieldContentType>, it’s already populated by default with the value application/json.

As example (with dummy values) : 

It works like a charm of me. I was able to edit  my custom connector in production environment as I used to do before this bug happened. I hope that those details explanations will help you 🙂

[rolign]

For me it started to work after removing a Connector from a solution, but does not seem to be the case for my colleague.

[mki1]

This solved it for me! Thank you so much, @Johanlb and @AlexTofan 😄

[tcibir]

Thank you for this. This worked very well

[mackemlad]

Um - Oh dear...

I'm embarrassed, but not too humble, to mention (if for no-one else, for the benefit of my future self) that it's important to remember the difference between a Custom ConnectOR and a Custom ConnectION.

Frankly, I've no idea whether I was bitten by the same bug reported by the OP because I was incorrectly trying to edit the connection and not the connector as part of updating the ALM Accelerator.  Having already gone through the steps provided by @AlexTofan (thanks again for that post) I was able to edit the connector without issue once I realized my mistake.

I learned a few things on my way to getting there, so it wasn't a wasted journey and I appreciate all the input that helped get me there.