You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: powerapps-docs/sample-apps/regional-emergency-response/deploy.md
+48-5Lines changed: 48 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -666,7 +666,7 @@ In this step, we will fix the **Send Password Reset To Contact** process to spec
666
666
667
667
5. If it’s not enabled, select the process name to open the record, and then select **Activate**. Confirm to activate the process.
668
668
669
-
## Step 13: Verify the Flow supply tracking flow is enabled
669
+
## Step 13: Enable the Flow supply tracking flow
670
670
671
671
1. Sign into [Power Automate](https://flow.microsoft.com/).
672
672
@@ -675,16 +675,59 @@ In this step, we will fix the **Send Password Reset To Contact** process to spec
675
675
> [!div class="mx-imgBorder"]
676
676
> 
677
677
678
-
3. In the solution, filter on **Flow** to find the **Flow supply tracking** record. Ensure that the status is set to **On**.
678
+
3. In the solution, filter on **Flow** to find the **Flow supply tracking** record.
679
679
680
680
> [!div class="mx-imgBorder"]
681
681
> 
682
682
683
-
4.If it is not set to **On**, select the flow name to open the flow definition.
683
+
4.Select the flow name to open the flow definition. In the flow definition, select **Edit** on the toolbar.
684
684
685
-
5.In the flow definition, select **Turn On** in the toolbar.
685
+
5.Fix the connection to connect to Common Data Service, and save the connection information.
686
686
687
-
## Step 14: Share admin app with other admin users
687
+
6. In the flow definition, select **Turn On**.
688
+
689
+
## Step 14: Update the details of flows for sending emails
690
+
691
+
In this step, we are going to do the following:
692
+
693
+
|Flow name|Changes|
694
+
|--|--|
695
+
|**Portal User Request: Send Email on Decline Request**|Update the connection to connect to Common Data Service and then should be used for sending the emails, like no-reply\@[*customerdomain*].com. This user account must be already set up in your environment with the server-side synchronization enabled.|
696
+
|**Portal User Request: Send Email to Admins on Request Creation**|Update the connection to connect to Common Data Service as a user account that should be used for sending the emails, like no-reply\@[*customerdomain*].com. This user account must be already set up in your environment with the server-side synchronization enabled. Additionally, update the portal URL in the email body as per your Portal URL.|
697
+
698
+
1. Sign into [Power Automate](https://flow.microsoft.com/).
699
+
700
+
2. In the left pane, select **Solutions.** From the solution list, select **Regional Emergency Response Solution** to open the solution.
701
+
702
+
> [!div class="mx-imgBorder"]
703
+
> 
704
+
705
+
3. In the solution, filter on **Flow** to find the flows.
706
+
707
+
> [!div class="mx-imgBorder"]
708
+
> 
709
+
710
+
4. Select the **Portal User Request: Send Email on Decline Request** name to open the flow definition. Select **Edit** on the toolbar.
711
+
712
+
5. Fix the connection to connect to Common Data Service by selecting **Connections** and then either using the existing connection using a new credential by selecting **Add new connection**.
6. using a user account that has the server-side synchronization enabled. and then save the flow.
718
+
719
+
> [!div class="mx-imgBorder"]
720
+
> 
721
+
722
+
6. In the flow definition, select **Turn On**.
723
+
724
+
7. Next, go to the flows list, and select the **Portal User Request: Send Email to Admins on Request Creation** name to open the flow definition. Select **Edit** on the command bar.
725
+
726
+
8. Fix the connection to connect to Common Data Service using a user account that has the server-side synchronization enabled and then save the flow.
727
+
728
+
729
+
730
+
## Step 15: Share admin app with other admin users
688
731
689
732
For your business admin users to use the admin app (model-driven app) to enter and manage data, it must be shared with them. It's easier to use Azure AD groups to easily share apps with a group of admin users.
## Step 7: Update the details of flows for sending emails
111
+
112
+
In this step, we are going to do the following:
113
+
114
+
|Flow name|Changes|
115
+
|--|--|
116
+
|**Portal User Request: Send Email on Decline Request**|Update the connection to connect to Common Data Service as a user account that should be used for sending the emails, like no-reply\@[*customerdomain*].com. This user account must be already set up in your environment with the server-side synchronization enabled.|
117
+
|**Portal User Request: Send Email to Admins on Request Creation**|Update the connection to connect to Common Data Service as a user account that should be used for sending the emails, like no-reply\@[*customerdomain*].com. This user account must be already set up in your environment with the server-side synchronization enabled. Additionally, update the portal URL in the email body as per your Portal URL.|
118
+
119
+
1. Sign into [Power Automate](https://flow.microsoft.com/).
120
+
121
+
2. In the left pane, select **Solutions.** From the solution list, select **Regional Emergency Response Solution** to open the solution.
122
+
123
+
> [!div class="mx-imgBorder"]
124
+
> 
110
125
111
-
## Step 7: Edit the 2 flows (check the recording)
126
+
3. In the solution, filter on **Flow** to find the **Flow supply tracking** record. Ensure that the status is set to **On**.
112
127
113
-
- Verifying the credentials to connect to CDS and send email
128
+
> [!div class="mx-imgBorder"]
129
+
> 
114
130
115
-
- In the 2nd flow, we are Verifying the credentials to connect to CDS and send
116
-
email and also fixing the Portal URL in the email body
131
+
4. If it is not set to **On**, select the flow name to open the flow definition.
117
132
118
-
After the flow is complete and next time Power BI report is refreshed (every 30
119
-
mins as per our recommendation), you will see the historical data in your
120
-
reports.
133
+
5. In the flow definition, select **Turn On** in the toolbar.
0 commit comments