cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
schuess3
Kudo Kingpin
Kudo Kingpin

SharePoint Action - We are unable to find the site address

I like many people on this forum have experienced this same issue. I have gone through related posts, but any proposed solutions do not work in my situation. If I were to guess, my scenario is either related to security or possibly a site setting that would hide the site from search or use with other applications or something related. The site in question belongs to the HR department and has been locked down tight by administrators. The account I am using to both build the flow and make the connection to SharePoint has access proven by the fact that I can navigate and browse the site. Since I am not the site admin, I cannot personally verify settings nor the level of access the account has been granted, but any suggestions as to why I may be seeing this behavior would be much appreciated.

 

As usual, the screen captures look like this

Get-Lists-Choices.pngGet-Lists-Custom-Value.png

 

Troubleshooting Steps Performed

  • Verified Account has Site Permissions
  • Created new flow from scratch
  • Entered custom value of site URL without ending /
  • Entered custom value of site URL with ending /

 

Any suggestions to try? @faustocapellanj @Flownaut @RezaDorrani @Shanescows @chass @Pstork1 

 

Thank you!

Matt

 

1 ACCEPTED SOLUTION

Accepted Solutions
schuess3
Kudo Kingpin
Kudo Kingpin

UPDATE

Thanks for the suggestion @Pstork1 . Turns out that was not the issue, but I was able to solve my issue.

 

Quick Background

This was a multi-developer, multi-environment MS Teams Power App built on Dataverse for Teams. In the development “teams” environment, multiple connection references were created because each dev had their own login. When deployment to the prod “teams” environment, we attempted to use a dedicated service account and one set of connection references. The ALM story has been a work in progress in this new citizen dev “low code” world. Since this was completely MS Teams based solution, I had always been creating cloud flows from within the team’s maker experience.

 

schuess3_0-1641570158021.png

 

Solving the problem

Using the dedicated prod service account, I decided to create a new flow in the standard flow.microsoft.com designer as opposed to inside of the team’s solution experience. Since this account had never created a connection reference to the SharePoint Site in the default flow environment, I needed to create a new connection. After adding a SharePoint action to the flow, I did not immediately see the elusive SharePoint HR site in the site drop down. I entered the URL using the “Enter custom value” option, but if I remember correctly, I still saw the “unable to find the site address” error. Funny thing is, I was able to pick from a correct list of libraries in the second attribute of the flow action. And after I did that, the “unable to find the site address” error went bye bye 😊. To make a long story short, I returned to the Teams environment, created a brand-new connection reference, and swap it for connection references that I had issues within other cloud flows used in the teams based solution.

 

schuess3_1-1641570158032.png

 

Solution Summary

Spoiler
Try recreating the connection reference.

(I hope this helps someone)

 

Bonus Tip

When creating service connections in a multi-dev scenario, create them with unique display names.

 

 

View solution in original post

2 REPLIES 2
Pstork1
Dual Super User
Dual Super User

Hiding the site from Search will keep it from showing up in the dropdown.  But if you use the Enter custom value to put in the actual URL it should still be recognized.  Just to check for sure.  You did enter the custom address after selecting the Enter Custom Value entry and not just by typing it in the dropdown.  Typing it will not work.  You have to use the Enter Custom Value entry. I'm assuming you did it the right way.  

 

The other thing you can check is to make sure that the admins haven't disabled Power Automate entirely for that site.  See this blog. SharePoint Online: How to Disable Microsoft Flow (Power Automate) in Lists and Libraries? - SharePoi...



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
schuess3
Kudo Kingpin
Kudo Kingpin

UPDATE

Thanks for the suggestion @Pstork1 . Turns out that was not the issue, but I was able to solve my issue.

 

Quick Background

This was a multi-developer, multi-environment MS Teams Power App built on Dataverse for Teams. In the development “teams” environment, multiple connection references were created because each dev had their own login. When deployment to the prod “teams” environment, we attempted to use a dedicated service account and one set of connection references. The ALM story has been a work in progress in this new citizen dev “low code” world. Since this was completely MS Teams based solution, I had always been creating cloud flows from within the team’s maker experience.

 

schuess3_0-1641570158021.png

 

Solving the problem

Using the dedicated prod service account, I decided to create a new flow in the standard flow.microsoft.com designer as opposed to inside of the team’s solution experience. Since this account had never created a connection reference to the SharePoint Site in the default flow environment, I needed to create a new connection. After adding a SharePoint action to the flow, I did not immediately see the elusive SharePoint HR site in the site drop down. I entered the URL using the “Enter custom value” option, but if I remember correctly, I still saw the “unable to find the site address” error. Funny thing is, I was able to pick from a correct list of libraries in the second attribute of the flow action. And after I did that, the “unable to find the site address” error went bye bye 😊. To make a long story short, I returned to the Teams environment, created a brand-new connection reference, and swap it for connection references that I had issues within other cloud flows used in the teams based solution.

 

schuess3_1-1641570158032.png

 

Solution Summary

Spoiler
Try recreating the connection reference.

(I hope this helps someone)

 

Bonus Tip

When creating service connections in a multi-dev scenario, create them with unique display names.

 

 

Helpful resources

Announcements
MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

New Process Advisor Capabilities carousel.png

Read the blog for the latest news

Read the latest about new experiences and capabilities in the Power Automate product blog.

PA Survey Carousel Image.png

We want to hear from you!

If you are a small business ISV/Reseller, share your thoughts with our research team.

AI Builder AMA June 7th carousel (up on May 25th, take down June 8th) (1).png

'Ask Microsoft Anything' about AI Builder!

The AI Builder team invite you to ask questions and provide helpful answers at our next AMA.

Top Kudoed Authors
Users online (1,506)