|
| 1 | +--- |
| 2 | +title: Upgrade the Regional Government Emergency Response and Monitoring solution | Microsoft Docs |
| 3 | +description: Provides provides detailed instructions for regional IT admins to upgrade the Regional Government Emergency Response and Monitoring solution for their organization. |
| 4 | +author: KumarVivek |
| 5 | +manager: annbe |
| 6 | +ms.service: powerapps |
| 7 | +ms.topic: conceptual |
| 8 | +ms.custom: |
| 9 | +ms.date: 04/29/2020 |
| 10 | +ms.author: kvivek |
| 11 | +ms.reviewer: kvivek |
| 12 | +searchScope: |
| 13 | + - PowerApps |
| 14 | +--- |
| 15 | + |
| 16 | +# Upgrade the Regional Government Emergency Response and Monitoring solution |
| 17 | + |
| 18 | +Perform the steps in this article to upgrade your existing installation of Regional Government Emergency Response and Monitoring solution to the latest version. |
| 19 | + |
| 20 | +## Prerequisites |
| 21 | + |
| 22 | +- Ensure that you have the Global Admin credentials and environment details where |
| 23 | + the Regional Government Emergency Response and Monitoring solution is deployed currently. |
| 24 | + |
| 25 | +- Ensure all users are disconnected from your environment before you upgrade. You might have to plan the upgrade process at a time when there is minimal obstructions for your users. |
| 26 | + |
| 27 | +- Ensure you have copied the Email contents to a Word file from the Send |
| 28 | + Invitation, Send Password Reset To Contact processes |
| 29 | + |
| 30 | +## Step 1: Download the upgrade deployment package |
| 31 | + |
| 32 | +Get the latest deployment package (.zip) from <https://aka.ms/rer-solution>. It's the same deployment package as the one you download during the fresh deployment step. |
| 33 | + |
| 34 | +**IMPORTANT:** Before extracting the .zip file, ensure that you unblock it. |
| 35 | + |
| 36 | +1. Right click the .zip file, select **Properties**. |
| 37 | + |
| 38 | +2. In the properties dialog box, select **Unblock**, and then select **Apply** |
| 39 | + followed by **OK.** |
| 40 | + |
| 41 | +After unblocking the file, extract the .zip file to see the following in the |
| 42 | +extracted folder: |
| 43 | + |
| 44 | +On extracting the .zip file, you will see the following in the extracted folder: |
| 45 | + |
| 46 | +|**Folder** |**Description** | |
| 47 | +|---------|---------| |
| 48 | +|**Package** | The folder contains the Package Deployer tool and the package that you will import later to set up the solution in your environment. | |
| 49 | +|**Power BI Template** | Contains the Power BI Report template file (.pbit) that you will use to configure reporting. More information: [Step 5: Configure and publish Power BI dashboard](#step-5-configure-and-publish-power-bi-dashboard) | |
| 50 | +|**SampleData** | Contains the sample master data files (.xlsx) that you can use to import sample data. | |
| 51 | + |
| 52 | +## Step 2: Install the upgrade package |
| 53 | + |
| 54 | +Install the upgrade package in the **same environment** where you have the |
| 55 | +existing solution installed. You can install the upgrade package in one of the following 3 ways just like you did when deploying the solution for the **first time**. |
| 56 | + |
| 57 | +- Microsoft AppSource (for Power Apps US Govt customers only). See [Option A: Install the app from Microsoft AppSource (US Govt customers)](#option-a-install-the-app-from-microsoft-appsource-us-govt-customers) in the deployment topic |
| 58 | + |
| 59 | +- Microsoft AppSource (for Power Apps commercial version customers). See [Option B: Install the app from Microsoft AppSource](#option-b-install-the-app-from-microsoft-appsource) in the deployment topic |
| 60 | + |
| 61 | +- Deployment package that you downloaded earlier. See [Option C: Install the app from the deployment package](#option-c-install-the-app-from-the-deployment-package) in the deployment topic |
| 62 | + |
| 63 | +## Step 3: Publish the latest Power BI dashboard |
| 64 | + |
| 65 | +Use the .pbit file in the upgrade package to configure and publish the latest |
| 66 | +Power BI dashboard. |
| 67 | + |
| 68 | +Steps to use the .pbit file are the same as the original deployment; make sure you use the same workspace to overwrite the existing Power BI dashboard if you want to preserver the Power BI report URL that is used for embedding it into Power Apps portal. |
| 69 | + |
| 70 | +More information: [Step 5: Configure and publish Power BI |
| 71 | +dashboard](https://docs.microsoft.com/powerapps/sample-apps/regional-emergency-response/deploy#step-5-configure-and-publish-power-bi-dashboard) |
| 72 | + |
| 73 | +## Step 4: Verify the Power BI report URL in your portal |
| 74 | + |
| 75 | +This step is required only if your Power BI report URL has changed in the previous step owing to you publishing the dashboard in a new worksoaceVerify the **PowerBI Path** site setting in your portal and update the value |
| 76 | +with the latest Power BI report URL. |
| 77 | + |
| 78 | +For detailed steps, see [Embed Power BI report in |
| 79 | +portal](https://docs.microsoft.com/en-us/powerapps/sample-apps/regional-emergency-response/deploy#the-process-1) |
| 80 | + |
| 81 | +Make sure to restart our portal for the changes to take effect. More |
| 82 | +information: [Restart the |
| 83 | +portal](https://docs.microsoft.com/en-us/powerapps/sample-apps/regional-emergency-response/deploy#restart-the-portal) |
| 84 | + |
| 85 | +## Step 5: Verify the Send Invitation and Send Password Reset To Contact processes |
| 86 | + |
| 87 | +Verify that the **Send Invitation** and **Send Password Reset To Contact** |
| 88 | +processes are still valid, that is, they have an account in the **From** field |
| 89 | +that can send emails and the rest of the details are fine. |
| 90 | + |
| 91 | +For details about how to fix these processes, see: |
| 92 | + |
| 93 | +- [Step 10: Fix the Send Invitation |
| 94 | + process](https://docs.microsoft.com/en-us/powerapps/sample-apps/regional-emergency-response/deploy#step-10-fix-the-send-invitation-process) |
| 95 | + |
| 96 | +- [Step 11: Fix the Send Password Reset To Contact |
| 97 | + process](https://docs.microsoft.com/en-us/powerapps/sample-apps/regional-emergency-response/deploy#step-11-fix-the-send-password-reset-to-contact-process) |
| 98 | + |
| 99 | +## Step 6: Verify the Flow supply tracking flow is enabled |
| 100 | + |
| 101 | + |
| 102 | +This flow enables the frontline user to add supplies through the portal that |
| 103 | +gets saved in Common Data Service. |
| 104 | + |
| 105 | +For details about how to fix these processes, see [Step 13: Verify the Flow |
| 106 | +supply tracking flow is |
| 107 | +enabled](https://docs.microsoft.com/en-us/powerapps/sample-apps/regional-emergency-response/deploy#step-13-verify-the-flow-supply-tracking-flow-is-enabled). |
| 108 | + |
| 109 | +## Step 7: Edit the 2 flows (check the recording) |
| 110 | + |
| 111 | +- Verifying the credentials to connect to CDS and send email |
| 112 | + |
| 113 | +- In the 2nd flow, we are Verifying the credentials to connect to CDS and send |
| 114 | + email and also fixing the Portal URL in the email body |
| 115 | + |
| 116 | +After the flow is complete and next time Power BI report is refreshed (every 30 |
| 117 | +mins as per our recommendation), you will see the historical data in your |
| 118 | +reports. |
| 119 | + |
0 commit comments