OfficeDev / microsoft-teams-apps-requestateam

Power Platform based solution that allows users to request teams and automates team creation.
MIT License
231 stars 64 forks source link

Check Availability Fails #164

Open AlanMRichards opened 3 years ago

AlanMRichards commented 3 years ago

The check availability button has an error and is not running. I have checked the App monitor in PowerApps and get a Bad Gateway error and this in the app.

image

alexc-MSFT commented 3 years ago

@AlanMRichards the most common reason for this error is that the data connections and variables inside the 'CheckTeamAvailability' flow have not been updated.

Did you update these as per the documentation?

Thanks

FernandoGualano commented 3 years ago

Hi! I had the same issue. The problem was I didn't modify the List Name under Check Team Availability Flow > Check site exists response > Check for existing requests matching URL. The Deployment Guide say:

image

But it doesn't say anything about modifying the "List Name" field. This field must be replaced by "Teams Requests", that is the List Name.

I hope it helps! Thanks!

eturinox commented 3 years ago

There is only the Team request Approval flow but not an Check Team Availability flow after importing the zip file? image

What did i do wrong? Thanks

FernandoGualano commented 3 years ago

There is only the Team request Approval flow but not an Check Team Availability flow after importing the zip file? image

What did i do wrong? Thanks

The "Check Team Availability" flow is imported when you import the Power App package as it is linked to the Power Apps (Step 3: Set up Power Apps). When you import this package, you should see the following:

image

ITAndy23 commented 2 years ago

I also see the badgateway error message. I have tried multiple browsers and signed-in as different Flow owners. I have deleted and recreated my SharePoint Flow connection. I have recreated the steps in the Flow where it references SharePoint, "Check if site exists" and "check for existing requests matching url". I confirmed they are pointing to the correct SPO site and in the 2nd step, the correct list on that site. I gave the user account site Owner and Site Collection Admin to the Request Teams Site I'm still getting the same error.

Update: I separated out the "Send an HTTP request to SharePoint" to its own independent flow. I still get the BadGateway error. I tried changing the Uri to use _api/web/lists/getbytitle('Documents') for testing. That worked. I got results. But _api/SP.Site.Exists is still giving an error.

BennySnatch commented 1 year ago

@alexc-MSFT; I've taken a look at this and the variable for "TeamsRequestSiteURL" is being used as the input for the "Send an HTTP request to SharePoint" step. This is incorrect.

image

image

Instead; the full tenant name should be used "https://m365x765471.sharepoint.com" with no site defined. Then you get the desired "true" or "false" result and not a 404.

Hope this is useful.

Cheers.

krhoadesnh commented 1 year ago

I still get the bad gateway error here, any ideas? image