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
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
Accepted Solutions
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.
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.
Solution Summary
(I hope this helps someone)
Bonus Tip
When creating service connections in a multi-dev scenario, create them with unique display names.
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.
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.
Solution Summary
(I hope this helps someone)
Bonus Tip
When creating service connections in a multi-dev scenario, create them with unique display names.
Helpful resources
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
We are excited to announce the Summer of Solutions Challenge! This challenge is kicking off on Monday, June 17th and will run for (4) weeks. The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities. Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”) - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024 Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods. You must enter into each weekly Entry Period separately. How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different. Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers. At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing. Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner. A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random. Individuals will be contacted before the announcement with the opportunity to claim or deny the prize. Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners. Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event. ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE** Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24 17 @Anil_g 7 @ManishSolanki 13 @eetuRobo 5 @David_MA 10 @VishnuReddy1997 5 @SpongYe 9JhonatanOB19932 (tie) @Nived_Nambiar 8 @maltie 2 (tie) @PA-Noob 2 (tie) @LukeMcG 2 (tie) @tgut03 2 (tie) Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate @Deenuji 12@ManishSolanki 19 @Anil_g 10 @NathanAlvares24 17 @VishnuReddy1997 6 @Expiscornovus 10 @Tjan 5 @Nived_Nambiar 10 @eetuRobo 3 @SudeepGhatakNZ 8 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2 Anil_g2 SharonS2
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages