4. Update - OfficeDev/TACO GitHub Wiki

Updates will be provided on a regular base. Updates which will be released will contain either:

  • bug fixes
  • code enhancements
  • new features based on feedback from the community

Depending on which enhancements have been made it could be that you will only need to update the Azure Function App while in other scenarios it might require you to update the PowerApp solution.

We are trying to avoid making changes to the SharePoint Online lists used by the App. However it could be that we are adding a new list or add columns to exists lists.

For all updates which are released we will provide an overview of what has been changed in the announcements section in the discussions part of this repository.

Update Azure Function App

Update Run from package version

By default the Azure Function App is running as a package. This means that when the Azure Function App starts or is being restarted it will download the latest package from the repository. This results in the Azure Function App part to be automatically updated. Keep in mind that since the tool has a dependency on the Teams PowerShell module you might need to perform the following additionals tasks if it is mentioned in the release notes:

  1. Go to the Azure Function App in the Azure portal
  2. From the left menu select Configuration
  3. In the Configuration section you will find the Application settings which contain the variables used by the App, search for TeamsPSVersion
  4. Click on the Click to show value link to show the current configured value
  5. If the value does not match the one mentioned in the release notes click on the pencil and adjust the value
  6. Click Save on the top of the page to save the change

Update self-hosted package

In case your organization has decided to implement the Azure Function App as a self-hosted package you will need to manually update the Azure Function App using the steps below:

  1. Go to the Azure Function App in the Azure portal
  2. From the left menu select Advanced Tools in the Development Tools section
  3. Select Debug Console on the top of the screen followed by PowerShell
  4. Wait till the page has loaded completely
  5. Click on site followed by wwwroot
  6. In case the release notes mention a new Teams PowerShell Module is required go to the Modules folder and remove the MicrosoftTeams folder completely
  7. Replace the content by dragging and dropping the content from the ZIP which you download from the repository
  8. Wait till the content upload has completed
  9. Go back to the Azure Function App page
  10. In the Configuration section you will find the Application settings which contain the variables used by the App, search for TeamsPSVersion
  11. Click on the Click to show value link to show the current configured value
  12. If the value does not match the one mentioned in the release notes click on the pencil and adjust the value
  13. Click Save on the top of the page to save the change
  14. Restart the Azure Function App

Update the PowerApp solution

The PowerApp solution will update both the PowerApp but also the workflows. Perform the steps below to update the existing version of TACO to the new version we do recommend to validate this in a separate environment prior to deploying in production

  1. Sign into Power Apps, select the target environment you want, and then select Solutions from the left navigation

  2. On the command bar, select Import

  3. On the Select Solution Package page, select Browse to locate the compressed (.zip or .cab) file that contains the solution you want to update

  4. Select Next

  5. This page displays a yellow bar indicating This solution package contains an update for a solution that is already installed. To upgrade the solution, select Next. To view additional options, expand Advanced settings, and then select from the following solution action options:

    • Upgrade This is the default option and upgrades your solution to the latest version and rolls up all previous patches in one step. Any components associated to the previous solution version that are not in the newer solution version will be deleted. This is the recommended option as it will ensure that your resulting configuration state is consistent with the importing solution including removal of components that are no longer part of the solution.

    • Stage for Upgrade This option upgrades your solution to the higher version, but defers the deletion of the previous version and any related patches until you apply a solution upgrade later. This option should only be selected if you want to have both the old and new solutions installed in the system concurrently so that you can do some data migration before you complete the solution upgrade. Applying the upgrade will delete the old solution and any components that are not included in the new solution.

    • Update This option replaces your solution with this version. Components that are not in the newer solution won't be deleted and will remain in the system. This option is not recommended as your destination environment will differ in configuration from your source environment and could cause issues that are difficult to reproduce and diagnose.

  6. Select Import

  7. You may need to wait a few moments while the solution import completes. If it's successful, you can view the results and select Close