Unanswered

Ambiguous connector names and descriptions

(1) Share

Report

Posted on by Baltner

149

Hello. I have three SharePoint connectors in my environment and they all have the same description (my email address) and a name of "SharePoint." This makes it hard to tell one from the other when I am selecting a connection in Power App studio. How can I rename or edit the description to disambiguate these connections? Thanks!

Categories:

Building Power Apps

All responses (4)

Answers (0)

Sort by

WarrenBelz 156,570 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @Baltner ,

When you find a way, let me know . . sorry, but the naming is what it is unfortunately

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

MVP (Business Applications) Visit my blog Practical Power Apps
markinwaukesha 96 on at

Like
a
(0)

Report
Copy link

Link copied!

The closest I've come is by exporting the component to find the GUID of the connector it's using.

So if you have three SharePoint connectors - get the GUID's of all of them, as well as the date created -

so when you go to "choose" the new connector you have a chance at getting a specific one.

Look up the GUID used by the actual power component - (the Yaml view may help here) - unfortunately you

cannot edit the Yaml for the power component yet - so you need to go into the edit view and update it for each

single one.

Having rename is a requested feature.

This also happens for Outlook and office365 connectors.

There are alot of issues around connectors of "referenced by" listings also (mostly with flows)
markinwaukesha 96 on at

Like
a
(0)

Report
Copy link

Link copied!

After thinking about my post below awhile, I wrote a Powershell to dump all my connections with name, and date, id

Probably the best way to solve this would be - using my example having three connectors all named the same with the email address

just delete two of them - so you're left with a single one (since they're all the same)

Then go through all the apps / flows and fix the references - Maybe on a Weekend or maintenance window.

Selecting the existing connection, saving, publishing is pretty quick even if you have 20-30 apps/flows.

it may seem drastic but the most efficient way. - if you're able to do this in a location / office where you have that access

it's probably the way to go.

Good luck
markinwaukesha 96 on at

Like
a
(1)

Report
Copy link

Link copied!

I wanted to add additionally:

it would be great on the Flows listing page - to be able to sort and filter -