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/developer/common-data-service/webapi/retrieve-related-entities-query.md
+94-49Lines changed: 94 additions & 49 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: "Retrieve related entity records with a query (Microsoft Dataverse)| Microsoft Docs"
3
3
description: "Read how you can retrieve related entity records by expanding the navigation properties."
4
4
ms.custom: ""
5
-
ms.date: 06/27/2020
5
+
ms.date: 11/16/2020
6
6
ms.service: powerapps
7
7
ms.suite: ""
8
8
ms.tgt_pltfrm: ""
@@ -207,9 +207,11 @@ OData-Version: 4.0
207
207
208
208
## Retrieve related entities by expanding collection-valued navigation properties
209
209
210
-
If you expand on collection-valued navigation parameters to retrieve related entities for entity sets, an `@odata.nextLink` property will be returned for the related entities. You should use the value of the `@odata.nextLink` property with a new `GET` request to return the required data.
210
+
If you expand on collection-valued navigation parameters to retrieve related entities for entity sets, only one level of depth is returned if there is data. Otherwise the collection will return an empty array.
211
211
212
-
The following example retrieves the tasks assigned to the top 2 account records.
212
+
In either case an `@odata.nextLink` property will be returned for the related entities. If you want to retrieve the collection separately, you can use the value of the `@odata.nextLink` property with a new `GET` request to return the required data.
213
+
214
+
The following example retrieves the tasks assigned to the top 2 account records. One has related tasks, the other does not.
## Retrieve related entities by expanding both single-valued and collection-valued navigation properties
257
281
258
-
The following example demonstrates how you can expand related entities for entity sets using both single- and collection-valued navigation properties. As explained earlier, expanding on collection-valued navigation properties to retrieve related entities for entity sets returns an `@odata.nextLink` property for the related entities. You should use the value of the `@odata.nextLink` property with a new `GET` request to return the required data.
282
+
The following example demonstrates how you can expand related entities for entity sets using both single and collection-valued navigation properties. As explained earlier, expanding on collection-valued navigation properties to retrieve related entities for entity sets returns one level of depth and an `@odata.nextLink` property for the related entities.
259
283
260
284
In this example, we are retrieving the contact and tasks assigned to the top 2 accounts.
Copy file name to clipboardExpand all lines: powerapps-docs/developer/model-driven-apps/clientapi/reference/Xrm-Navigation/openForm.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ search.app:
44
44
<li><b>height</b>: (Optional) Number. Height of the form window to be displayed in pixels.</li>
45
45
<li><b>navbar</b>: (Optional) String. Controls whether the navigation bar is displayed and whether application navigation is available using the areas and subareas defined in the sitemap. Valid values are: "on", "off", or "entity".<ul><li><code>on</code>: The navigation bar is displayed. This is the default behavior if the <b>navbar</b> parameter is not used.</li>
46
46
<li><code>off</code>: The navigation bar is not displayed. People can navigate using other user interface elements or the back and forward buttons.</li><li><code>entity</code>: On an entity form, only the navigation options for related entities are available. After navigating to a related entity, a back button is displayed in the navigation bar to allow returning to the original record.</li></ul></li>
47
-
<li><b>openInNewWindow</b>: (Optional) Boolean. Indicates whether to display form in a new window.</li>
47
+
<li><b>openInNewWindow</b>: (Optional) Boolean. Indicates whether to display form in a new window or a new tab. If you specify <code>true</code> and do not specify values for height or width, the form will display in a new tab.</li>
48
48
<li><b>windowPosition</b>: (Optional) Number. Specify one of the following values for the position of the form on the screen:<ul><li><code>1:center</code></li><li><code>2:side</code></li></ul>
49
49
This does not apply to opening a new browser window.
50
50
<li><b>relationship</b>: (Optional) Object. Define a relationship object to display the related records on the form. The object has the following attributes.
Copy file name to clipboardExpand all lines: powerapps-docs/maker/canvas-apps/build-responsive-apps.md
-2Lines changed: 0 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -17,8 +17,6 @@ search.app:
17
17
18
18
# Building responsive apps
19
19
20
-
[This article is pre-release documentation and is subject to change.]
21
-
22
20
Responsiveness refers to the ability of an app to automatically align to different screen sizes and form factors to use the available screen space sensibly, providing great UI and UX in every device, form factor, and screen size.
Copy file name to clipboardExpand all lines: powerapps-docs/maker/canvas-apps/geospatial-overview.md
+8-1Lines changed: 8 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,8 @@ The following prebuilt components can be used for geospatial and mapping scenari
32
32
## Prerequisites
33
33
34
34
1. An admin must [enable the geospatial features in the Power Platform admin center](#enable-the-geospatial-features-for-the-environment) for the environment. This requires reviewing and agreeing to specific terms of service.
35
-
2.[Enable the geospatial features for each app](#enable-the-geospatial-features-for-each-app).
35
+
2. An admin must [ensure the geospatial components will not be blocked by the environment's data loss prevention policies](#review-the-environments-data-loss-prevention-policies).
36
+
3.[Enable the geospatial features for each app](#enable-the-geospatial-features-for-each-app).
36
37
37
38
>[!IMPORTANT]
38
39
>The components require the default **Organizations** data source to be present. This data source is included whenever you insert the components into an app, but if you manually delete it you'll need to add it before the components will work:
@@ -85,6 +86,12 @@ The geospatial features require additional terms of use that must be reviewed an
85
86
86
87

87
88
89
+
### Review the environment's data loss prevention policies
90
+
91
+
The geospatial components require the Common Data Service and Spatial Services connectors.
92
+
93
+
For the components to function properly, these connectors must not have conflicting data loss prevention policies. An admin must review the environment's data loss prevention policies and ensure that these connectors are classified under the same data group, typically the **Business** data group. [Learn more about data loss prevention policies for Power Platform](/power-platform/admin/prevent-data-loss).
94
+
88
95
### Enable the geospatial features for each app
89
96
90
97
1. Open the app for editing in Power Apps Studio at [https://create.powerapps.com](https://create.powerapps.com).
0 commit comments