Skip to content

Commit 172da85

Browse files
authored
Live publish
2 parents 7af0aa0 + 735061e commit 172da85

22 files changed

+156
-5
lines changed

powerapps-docs/developer/data-platform/catalog-catalogassignment.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Catalog and CatalogAssignment tables (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
33
description: "Learn how to use the Catalog and CatalogAssignment tables to expose events in your solution"
44
ms.custom: ""
5-
ms.date: 07/06/2021
5+
ms.date: 07/12/2021
66
ms.reviewer: "pehecke"
77
ms.service: powerapps
88
ms.topic: "article"
@@ -251,13 +251,13 @@ GET [Organization URI]/api/data/v9.2/customapis?$select=customapiid&$filter=uniq
251251
This is most easily done using the Web API. The following example will return the `workflowid` of a custom process action with the `uniquename` of `ExampleCustomProcessAction`.
252252

253253
```http
254-
GET [Organization URI]/api/data/v9.2/workflows?$select=workflowid,uniquename&$filter=category eq 3 and type eq 2 and endswith(uniquename,'ExampleCustomProcessAction')
254+
GET [Organization URI]/api/data/v9.2/workflows?$select=workflowid,uniquename&$filter=category eq 3 and type eq 1 and endswith(uniquename,'ExampleCustomProcessAction')
255255
```
256256

257257
> [!NOTE]
258258
> The `uniquename` of the workflow doesn't include the customization prefix that is prepended to the name of the custom process action in the Web API. If the action you call from the Web API is named `new_ExampleCustomProcessAction`, the workflow uniquename will be `ExampleCustomProcessAction`.
259259
>
260-
> Make sure you to access the row where [Type](/powerapps/developer/data-platform/reference/entities/workflow#BKMK_Type) is `2`. This is the activated workflow.
260+
> Make sure you to access the row where [Type](/powerapps/developer/data-platform/reference/entities/workflow#BKMK_Type) is `1`. This is the workflow definition.
261261
>
262262
> Custom process action workflows have the [Category](/powerapps/developer/data-platform/reference/entities/workflow#BKMK_Category) value of `3`.
263263

powerapps-docs/developer/data-platform/troubleshoot-plug-in.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Troubleshoot plug-ins (Microsoft Dataverse for Apps) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
33
description: "Learn what plug-in errors can occur and how to fix them." # 115-145 characters including spaces. This abstract displays in the search result.
44
ms.custom: ""
5-
ms.date: 03/16/2021
5+
ms.date: 07/12/2021
66
ms.reviewer: "pehecke"
77
ms.service: "powerapps"
88
ms.topic: "article"
@@ -24,7 +24,7 @@ This topic contains information about errors that can occur due to plug-in execu
2424
## Error: No Sandbox Worker processes are currently available
2525

2626
Error Code: `-2147204723`<br />
27-
Error Message: `The plug-in execution failed because no Sandbox Worker processes are currently available. Please try again.`
27+
Error Message: `The plug-in execution failed because no Sandbox Hosts are currently available.`
2828

2929
This error simply means that the worker process running your plug-in code crashed. The reason it crashed may be your plug-in, but it could also be another plug-in running concurrently for your organization. Because the process crashed, we can’t extract any more specific information about why it crashed. But after examining data from the crash dumps after the fact, we have found that this usually happens for one of the 4 reasons below:
3030

powerapps-docs/maker/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2266,6 +2266,8 @@
22662266
href: ../teams/customize-inspections.md
22672267
- name: Add hierarchy inspection ___location
22682268
href: ../teams/inspections-hierarchy-locations.md
2269+
- name: Customize inspection steps
2270+
href: ../teams/customize-inspection-steps.md
22692271
- name: Issue reporting
22702272
items:
22712273
- name: Issue reporting
Lines changed: 149 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,149 @@
1+
---
2+
title: Customize Inspection Steps
3+
description: Learn about how the steps followed in the Inspection sample apps can be customized
4+
author: sbahl10
5+
ms.service: powerapps
6+
ms.topic: conceptual
7+
ms.custom:
8+
ms.date: 07/12/2021
9+
ms.author: v-shrutibahl
10+
ms.reviewer: tapanm
11+
contributors:
12+
- joel-lindstrom
13+
- navjotm
14+
- tapanm-msft
15+
- sbahl10
16+
---
17+
18+
# Inspections App – Customize inspection steps
19+
20+
The Inspections sample app allows users to create and perform inspections in the app. There are three apps, one per persona to perform, manage, and review Inspections. The three apps are&mdash;Inspections, Manage Inspections and Review Inspections.
21+
22+
In this article, we'll learn how to customize inspection steps in the user app. For example, removing the ability to add pictures to checklist steps. This customization is important because just deleting the particular control can cause issues with responsiveness, and the look and feel of the app can get affected.
23+
24+
## Prerequisites
25+
26+
To complete this lesson, we'd need the ability to sign-in to Microsoft Teams that will be available as part of select Microsoft 365 subscriptions, and will also need to have the Inspections sample app for Teams installed. This app can be installed from <https://aka.ms/TeamsInspection>.
27+
28+
## Open the Inspections app
29+
30+
1. Login into Teams, and right-click Power Apps from the left-pane, and select **Pop out app**.
31+
1. Select **Build** from the top ribbon.
32+
1. Select the team where the Inspections app is installed.
33+
1. Select Inspections to open the app in the editor.
34+
35+
![Open Inspection app](media/customize-inspection-steps/open-inspection-app.png "Open Inspection app")
36+
37+
1. Select the tree view from the left-pane.
38+
39+
1. Select to open the Items screen.
40+
41+
![Items Screen](media/customize-inspection-steps/items-screen.png "Items Screen")
42+
43+
1. Press **Alt** key on the keyboard, and select Ambient or Backstage to open the record. The Food Inspection checklists page opens.
44+
45+
1. Press **Alt** key on the keyboard, and select any one of the options (Detailed Walk/Morning Store Walk). The Inspection Overview screen appears.
46+
47+
1. Press **Alt** key on the keyboard, and select **Begin Inspection**. The Inspection list screen opens.
48+
49+
![Inspection List Screen](media/customize-inspection-steps/inspection-list-screen.png "Inspection List Screen")
50+
51+
1. This article explains the following scenarios:
52+
53+
- [Hide the Add details section](#hide-the-add-details-section)
54+
55+
![Hide Add Details Section](media/customize-inspection-steps/hide-add-details-section.png "Hide Add Details Section")
56+
57+
- [Hide just the Photo option](#hide-the-photo-option)
58+
59+
![Hide Photo Option](media/customize-inspection-steps/hide-photo-option.png "Hide Photo Option")
60+
61+
- [Hide the Task option](#hide-the-task-option)
62+
63+
![Hide Task Option](media/customize-inspection-steps/hide-task-option.png)
64+
65+
## Hide the Add Details section
66+
67+
Hiding the Add Details section includes more than just setting the Visible property of all those controls to False.
68+
69+
1. Set the **Visible** property for the **Add details** label, and the other labels (Photo, Note, and Task) and their icons to "False".
70+
71+
![Add Details Label visibility False](media/customize-inspection-steps/lbladddetails-visible-false.png "Add Details Label")
72+
73+
![Photo Container grpPhoto visibility False](media/customize-inspection-steps/photo-visible-false.png "Photo Container grpPhoto visibility False")
74+
75+
1. Set the **Visible** property for **grpNote**, **grpTask**, and **grpPhoto** to "False".
76+
77+
![All icons visibility False](media/customize-inspection-steps/all-icons-visible-false.png "All icons visibility False")
78+
79+
1. We'll also need to shrink the white space containing the Photo, Note, and Task buttons to avoid wasting any extra space. Select **btnActionBackground** control from the tree view, select somewhere on the white space to highlight the box space.
80+
81+
![Adjust Button Background](media/customize-inspection-steps/adjust-button-background.png "Adjust Button Background")
82+
83+
1. Open the **Height** property of the control, and comment the existing formula with `//` at the beginning of each line.
84+
85+
1. Add the following formula.
86+
87+
```powerapps-dot
88+
btnOK.Y + btnOK.Height - Self.Y + 20
89+
```
90+
91+
![Adjust Button Height](media/customize-inspection-steps/adjust-button-height.png "Adjust Button Height")
92+
93+
The white space shrinks, and leaves no extra space hiding the entire **Add Details** section.
94+
95+
## Hide the Photo Option
96+
97+
This scenario requires to revert all the changes made above. And then, we'll have to set the **Visible** property of the Photo option label, and icon to "False", and then move the Note option and the Task Options to the left.
98+
99+
1. To hide the Photo option, select **grpPhoto** from the tree view, and set **Visible** property to "False".
100+
101+
![Photo visibility set to False](media/customize-inspection-steps/set-grpphoto-visible-false.png "Photo visibility set to False")
102+
103+
1. The Note option needs to move to the left in place of the Photo option. Copy the X property of the Photo Icon and paste it in the X property of the Note icon (notice that the label also moves along with the icon&mdash;this is because the Note label’s X property is dependent on the Note icon’s X property, and changes accordingly thus leaving no empty spaces – the Task option also reacts similarly).
104+
105+
```powerapps-dot
106+
btnImageBackground.X+18
107+
```
108+
109+
![Adjust X position of Note icon](media/customize-inspection-steps/adjust-note-icon-x.png "Adjust X position of Note icon")
110+
111+
## Hide the Task Option
112+
113+
This scenario requires to revert all the changes made above. With this scenario, we only want to hide the Task section.
114+
115+
Change the **Visible** property for **grpTask** to "False".
116+
117+
![Task visibility set to False](media/customize-inspection-steps/set-grptask-visible-false.png "Task visibility set to False")
118+
119+
## Publish the Inspection app
120+
121+
All the changes to the Inspection app are completed.
122+
123+
1. Select **Publish to Teams** on the top-right.
124+
125+
![Publish to Teams](media/customize-inspection-steps/publish-to-teams.png "Publish to Teams")
126+
127+
1. Select **Next**.
128+
129+
![Confirm publishing to Teams](media/customize-inspection-steps/confirm-publishing-to-teams.png "Confirm publishing to Teams")
130+
131+
1. Select **Save and close**.
132+
133+
![Add app to Channel](media/customize-inspection-steps/add-to-channel.png "Add app to Channel")
134+
135+
## Test the app
136+
137+
On the Inspection list screen, once you make the change for any of the above listed scenarios, select **Preview** to run the app.
138+
139+
Make sure to check for responsiveness by shrinking the size of the screen when testing in the Window mode.
140+
141+
### See also
142+
143+
- [Understand Inspection sample apps architecture](inspection-architecture.md)
144+
- [Customize Inspection sample app](customize-inspections.md)
145+
- [Customize sample apps](customize-sample-apps.md)
146+
- [Sample apps FAQs](sample-apps-faqs.md)
147+
- [Use sample apps from the Teams store](use-sample-apps-from-teams-store.md)
148+
149+
[!INCLUDE[footer-include](../includes/footer-banner.md)]
Loading
Loading
Loading
Loading
Loading
Loading

0 commit comments

Comments
 (0)