Troubleshooting - OfficeDev/microsoft-teams-apps-requestateam GitHub Wiki

General template issues

Generic possible issues

Below are certain issues that are common to Power Apps app templates.

Problems deploying to a tenant

1. Cannot find the data source “Data source name”.

Reasons: This error usually occurs when SharePoint site/list does not exist or it belongs to a different tenant.

Fix: Navigate to the Power Apps portal and edit the app.

Ensure the SharePoint list you created is added properly, refresh the data connection and Save the file.

Problems related to PowerShell script

1. Cannot run PowerShell script

While running PowerShell script, sometimes user gets 'SharePointpnp error'.

Fix: If this type of error occurs then run this: "Install-Module SharePointPnPPowerShellOnline"

2. File is not digitally signed

While running PowerShell script, sometimes user gets an error showing 'File is not digitally signed'.

Fix: If this type of error occurs then run this: "Set-ExecutionPolicy -ExecutionPolicy unrestricted"

3. Error regarding Logic App deployment.

While running PowerShell script, sometimes user gets an error showing 'Logic app deployment failed'.

Fix: If this type of error occurs then in your Azure account go to API Connections, click on Edit, followed by Authorize (must be authorized by service account) and then Save.

4. Error regarding Team Request Approval flow.

If the flow is not triggered or failed.

Fix:Click on each step and check all the SharePoint site connections and its values as per deployment guide.

5. Team is not created even after approval

If the logic app is not triggered even after the status of requested team is approved.

Fix: Navigate to azure resource group created for this application and reauthenticate all five API connections by clicking on 'Edit API connection' on the left pane,using service account and also edit ProcessTeamRequest logic app and check all sharepoint connections(i.e When an item is created or modified,Update status to Team Creation and Update status to Team Created)

6. Status of request is Team Creation for more than a day.

The status will be changed from Approved to Team Creation once the logic app is triggered. If the requested team status is Team Creation for more than a day consider logic app is failed. Fix: Check the service accounted used while deployment has minimum E3 license and reauthenticate all API connections API connections by clicking on 'Edit API connection' on the left pane,using service account.

Note: If configured logic app properly, the only known case where logic app fails is when the selected owner or member is an unlicensed user in Office365.

7. Adaptive card failed to post to the Teams channel.

This may be because the 'Power Automate' and 'Power Automate Actions' apps are not allowed in the Teams permission policy in the admin center. If you have a permissions policy configured then you will need to allow these apps in order for the adaptive card to work.

8. Owners and/or Members combo boxes not showing results.

This is a bug in the current version of the Power App, a future responsive replacement Power App will fix this issue. To remediate the issue manually, follow the steps below:

  1. Edit the Power App.
  2. In the search box under 'Tree view' enter the following - 'cmbOwners'.
  3. Select the combo box control in the tree view.
  4. Expand the property pane on the right hand side.
  5. Locate the 'Allow multiple selections' and 'Allow searching' properties, toggle these to 'off' using the radio button then immediately toggle them back to on.
  6. Repeat the above for each owner combo box displayed in the search results - 'cmbOwners_2','cmbOwners_1','cmbOwners._2','cmbOwners._1','cmbOwners.'.
  7. Clear the search box.
  8. Enter the following text in the search box - 'cmbMembers'.
  9. Follow the steps above for each combo box displayed - 'cmbMembers' and 'cmbMembers.'.
  10. Save the Power App by clicking 'File' > 'Save'.
  11. Publish the Power App by clicking 'Publish'.

Re-open the Power App through Teams, this issue should now be fixed.

Didn't find your problem here?

Please, report the issue here