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
You can add informational cards to each pin on the map.
140
+
141
+
When a user selects the pin (either by hovering over it or selecting it directly), a small card will pop-up with information taken from the dataset you bound to the component, as described in the section [Use the map component with data from Excel](#use-the-map-component-with-data-from-excel).
142
+
143
+
Any column you add to the table in the data source (for example, the Excel table) will be available as a field to show on the card.
144
+
145
+
**To add informational cards to pins:**
146
+
147
+
1. First, insert the map component and bind a dataset to it as described in [Use the map component with data from Excel](#use-the-map-component-with-data-from-excel).
148
+
149
+
2. In the **Properties** pane, select **Show info cards** and choose whether they should appear when a user hovers over the pin, or if the user has to select the pin.
150
+
151
+
:::image type="content" source="media/geospatial/map-info-card-type.png" alt-text="Screenshot of the properties pane showing the drop-down selection menu to show the cards on hover or on click.":::
152
+
153
+
3. In the **Properties** pane, next to **Fields**, select **Edit**.
154
+
155
+
4. Select **Add field**, and then select each of the fields you want to show in the card. Select **Add**.
156
+
157
+
:::image type="content" source="media/geospatial/map-choose-fields.png" alt-text="Screenshot showing the field selection options.":::
158
+
159
+
5. Each pin will now show the fields associated with that pin in an informational card.
160
+
161
+
:::image type="content" source="media/geospatial/map-info-card-example.png" alt-text="Screenshot of the map component with an info card on top of a pin, showing information such as Name, Occupancy, and Phone.":::
162
+
136
163
### Properties
137
164
138
165
The following properties can be defined and configured in the component's **Properties** pane.
Copy file name to clipboardExpand all lines: powerapps-docs/maker/canvas-apps/mixed-reality-component-measure-distance.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,7 @@ With an app open for editing in [Power Apps Studio](https://create.powerapps.com
52
52
You can modify the component with a number of properties.
53
53
54
54
> [!NOTE]
55
-
> Your 3D content must be in the .glb file format. You can [convert your existing 3D models into the .glb file format](/dynamics365/mixed-reality/import-tool/) from a variety of 3D formats.
55
+
> Your 3D content must be in the .glb file format. You can [convert your existing 3D models into the .glb file format](/dynamics365/mixed-reality/guides/3d-content-guidelines/) from a variety of 3D formats.
Copy file name to clipboardExpand all lines: powerapps-docs/maker/canvas-apps/mixed-reality-component-view-3d.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ You can display a single 3D model, or you can let the user select from a gallery
28
28
29
29
> [!IMPORTANT]
30
30
> Your 3D content must be in the .glb file format.
31
-
> You can [convert your existing 3D models into the .glb file format](/dynamics365/mixed-reality/import-tool/) from a variety of 3D formats.
31
+
> You can [convert your existing 3D models into the .glb file format](/dynamics365/mixed-reality/guides/3d-content-guidelines/) from a variety of 3D formats.
32
32
33
33
To use the component, you need to [enable the mixed reality (MR) features for each app](mixed-reality-overview.md#enable-the-mixed-reality-features-for-each-app) that you want to use it in.
Copy file name to clipboardExpand all lines: powerapps-docs/maker/canvas-apps/mixed-reality-component-view-mr.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ You can also take photos and [upload them to OneDrive](mixed-reality-take-upload
29
29
30
30
> [!IMPORTANT]
31
31
> Your 3D content must be in the .glb file format.
32
-
> You can [convert your existing 3D models into the .glb file format](/dynamics365/mixed-reality/import-tool/) from a variety of 3D formats.
32
+
> You can [convert your existing 3D models into the .glb file format](/dynamics365/mixed-reality/guides/3d-content-guidelines/) from a variety of 3D formats.
33
33
34
34
To use the component, you need to [enable the mixed reality (MR) features for each app](mixed-reality-overview.md#enable-the-mixed-reality-features-for-each-app) that you want to use it in.
Copy file name to clipboardExpand all lines: powerapps-docs/maker/portals/configure/entity-forms.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -131,7 +131,7 @@ This provides a way to associate the current record being created or updated by
131
131
|Entity Logical Name|The logical name of the reference entity.|
132
132
|Target Lookup Attribute Logical Name|Logical name of the lookup attribute on the target entity being created or updated.|
133
133
|Populate Lookup Field| If the lookup regarding the reference entity is on the form, checking this value will populate the field on the form with the value retrieved using the setting below.|
134
-
|Reference Entity Source Type| One of the following values:<ul><li>Query String</li><li>Current Portal User</li><li>Result From Previous Step</li></ul> Selecting _Query String_ requires a parameter name that must be provided in the query string of the URL to the form. This can be specified in the **Query String Name** field. If this parameter is the primary key then select Yes for the **Query String Is Primary Key**, otherwise select No and provide the logical name of the attribute on the target entity to query by specified in the **Query Attribute Logical Name** field.Selecting Current Portal User will retrieve the contact record for the current authenticated user. Selecting Result From Previous Step will retrieve the record created as a result of the step prior to the current step or from a specific step based on the step associated with the Entity Source Step.|
134
+
|Reference Entity Source Type| One of the following values:<ul><li>Query String <br> Selecting _Query String_ requires a parameter name that must be provided in the query string of the URL to the form. This can be specified in the **Query String Name** field. If this parameter is the primary key then select Yes for the **Query String Is Primary Key**, otherwise select No and provide the logical name of the attribute on the target entity to query by specified in the **Query Attribute Logical Name** field.</li><li>Current Portal User <br> Selecting Current Portal User will retrieve the contact record for the current authenticated user.</li></ul>|
135
135
|Reference Entity Step| The Web Form Step record of a previous step to retrieve the entity created or edited in that step to associate it with the record for this current step.|
136
136
|Query String Name| Parameter name provided in the Query String of the URL to the Web Page containing the Web Form.|
137
137
|Query String Is Primary Key| Yes indicates the Query String value is the Primary Key value. No indicates the Query String value is an attribute type other than the Primary Key.|
Copy file name to clipboardExpand all lines: powerapps-docs/maker/portals/configure/load-form-step.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ This step type allows the web form step to act as an entity form within the over
24
24
| Tab Name | The name of a Tab on a Form for a specified entity that is to be rendered. Optional |
25
25
| Mode | One of the following values:<br><ul><li>Insert</li><li>Edit</li><li>ReadOnly</li></ul>Selecting Insert indicates the form should insert a new record upon submission. Specifying Edit indicates the form should edit an existing record. Selecting ReadOnly indicates the form should display an existing record's noneditable form. Edit and ReadOnly requires that a source record exist and parameters specified in the 'Record Source Type' and 'Record ID Query String Parameter Name' fields to select the appropriate record when the form is loaded in the portal. |
26
26
| Auto Generate Steps From Tabs | Checked indicates that multiple tabs on an entity form will be displayed with each tab as a sequential step starting with the first tab and continue until all tabs have been navigated to and upon final submission a record is inserted. Unchecked is the default behavior. Unchecked value indicates that only one tab or form is to be rendered for the current step. If the Tab Name is not specified, the first tab is displayed. |
27
-
| Record Source Type | One of the following values:<br><ul><li>Query String</li><li>Current Portal User</li><li>Result From Previous Step</li></ul>Selecting Query String requires a parameter name that must be provided in the query string of the URL to the form. This can be specified in the 'Record ID Query String Parameter Name' field.Selecting Current Portal User will retrieve the portal user record for the current authenticated user.<br>Selecting Result from previous step will retrieve the record that was the record source for a previous step of the web form. |
27
+
| Record Source Type | One of the following values:<br><ul><li>Query String <br> Selecting Query String requires a parameter name that must be provided in the query string of the URL to the form. This can be specified in the 'Record ID Query String Parameter Name' field.</li><li>Current Portal User <br> Selecting Current Portal User will retrieve the portal user record for the current authenticated user.</li></ul>|
28
28
| Record ID Query String Parameter Name | A parameter name provided in the query string of the URL to the Web Page containing this Entity Form. |
29
29
| Relationship Name | Required when Record Source Type is Record Associated to Current Portal User. The logical name of the relationship between the current portal user record and the target record. This must return the same entity type specified by the Entity Name field. |
30
30
| Allow Create If Null | An optional Boolean value available when Record Source Type is Record Associated to Current Portal User. Checked indicates that if the related record does not exist, allow the user to create it the first time, otherwise an exception will be thrown if the record does not already exist because the form needs a record to data-bind to. |
@@ -85,7 +85,7 @@ This provides a way to associate the current record being created or updated by
85
85
| Entity Logical Name | The logical name of the reference entity. |
86
86
| Target Lookup Attribute Logical Name | Logical name of the lookup attribute on the target entity being created or updated. <br>**Note**: Do not specify a relationship name if you specify a Target Lookup Attribute Logical Name. |
87
87
| Populate Lookup Field | If the lookup regarding the reference entity is on the form, checking this value will populate the field on the form with the value retrieved using the setting below. |
88
-
| Source Type | One of the following values:<ul><li>Query String</li><li>Current Portal User</li><li>Result From Previous Step</li></ul>Selecting Query String requires a parameter name that must be provided in the query string of the URL to the form. This can be specified in the **Query String Name** field. If this parameter is the primary key then select Yes for the **Query String Is Primary Key**, otherwise select No and provide the logical name of the attribute on the target entity to query by specified in the **Query Attribute Logical Name** field.Selecting Current Portal User will retrieve the contact record for the current authenticated user. Selecting Result From Previous Step will retrieve the record created as a result of the step prior to the current step or from a specific step based on the step associated with the Entity Source Step.|
88
+
| Source Type | One of the following values:<ul><li>Query String <br> Selecting Query String requires a parameter name that must be provided in the query string of the URL to the form. This can be specified in the **Query String Name** field. If this parameter is the primary key then select Yes for the **Query String Is Primary Key**, otherwise select No and provide the logical name of the attribute on the target entity to query by specified in the **Query Attribute Logical Name** field.</li><li>Current Portal User <br> Selecting Current Portal User will retrieve the contact record for the current authenticated user. </li></ul> |
89
89
| Reference Entity Step | The Web Form Step record of a previous step to retrieve the entity created or edited in that step to associate it with the record for this current step. |
90
90
| Query String Name | Parameter name provided in the Query String of the URL to the Web Page containing the Web Form. |
91
91
| Query String Is Primary Key | Yes indicates the Query String value is the Primary Key value. No indicates the Query String value is an attribute type other than the Primary Key. |
Copy file name to clipboardExpand all lines: powerapps-docs/teams/employee-ideas.md
+3Lines changed: 3 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,9 @@ Employee ideas app is used by the Teams users to perform the following activitie
33
33
> - Before you can use this app, you may be asked for your permissions to use the connection. More information: [Allow connections in sample apps](use-sample-apps-from-teams-store.md#step-1---allow-connections)
34
34
> - This app is available in three different Teams themes: Default, Dark and High contrast. When you [change the theme in Teams](https://support.microsoft.com/en-us/office/change-settings-in-teams-b506e8f1-1a96-4cf1-8c6b-b6ed4f424bc7), the app automatically updates to match the selected theme. More information: [Get the Teams theme using the Teams integration object](use-teams-integration-object.md#get-the-teams-theme)
35
35
36
+
> [!TIP]
37
+
> For a demonstration of how to use this app, watch this [video](https://aka.ms/TeamsEmployeeIdeasVideo).
0 commit comments