Merge pull request #6471 from MicrosoftDocs/main

tapanm-MSFT · web-flow · commit 6fcf65f6ad49 · 2022-06-03T09:30:55.000-07:00
custom page GA live
diff --git a/powerapps-docs/developer/data-platform/webapi/retrieve-entity-using-web-api.md b/powerapps-docs/developer/data-platform/webapi/retrieve-entity-using-web-api.md
@@ -1,7 +1,7 @@
 ---
 title: "Retrieve a table row using the Web API (Microsoft Dataverse)| Microsoft Docs"
 description: "Read how to form a GET request using the Microsoft Dataverse Web API to retrieve table data specified as the resource with a unique identifier"
-ms.date: 04/19/2022
+ms.date: 06/03/2022
 author: divka78
 ms.author: dikamath
 ms.reviewer: jdaly
@@ -416,7 +416,7 @@ The following example specifies that related tasks should be returned in ascendi
 > [!NOTE]
 > - Nested `$expand` options can only be applied to single-valued navigation properties.
 >
-> - Each request can include a maximum of 10 `$expand` options. There is no limit on the depth of nested `$expand` options, but the limit of 10 total `$expand` options applies to these as well.
+> - Each request can include a maximum of 15 `$expand` options. There is no limit on the depth of nested `$expand` options, but the limit of 15 total `$expand` options applies to these as well.
 >
 > - This is a subset of the system query options described in the “11.2.4.2.1 Expand Options” section of [OData Version 4.0 Part 1: Protocol Plus Errata 02](https://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-protocol/odata-v4.0-errata02-os-part1-protocol-complete.html). The options `$skip`, `$count`, `$search`, and `$levels` aren’t supported for the Web API.
 
diff --git a/powerapps-docs/developer/data-platform/webapi/retrieve-related-entities-query.md b/powerapps-docs/developer/data-platform/webapi/retrieve-related-entities-query.md
@@ -1,7 +1,7 @@
 ---
 title: "Retrieve related table records with a query (Microsoft Dataverse)| Microsoft Docs"
 description: "Read how you can retrieve related table records by expanding the navigation properties."
-ms.date: 04/06/2022
+ms.date: 06/03/2022
 author: divka78
 ms.author: dikamath
 ms.reviewer: jdaly
@@ -28,7 +28,7 @@ Use the `$expand` system query option in the navigation properties to control wh
 If you include only the name of the navigation property, you’ll receive all the properties for related records. You can limit the properties returned for related records using the `$select` system query option in parentheses after the navigation property name. Use this for both single-valued and collection-valued navigation properties.  
 
 > [!NOTE]
->  - You are limited to no more than 10 `$expand` options in a query. This is to protect performance. Each `$expand` options creates a join that can impact performance. 
+>  - You are limited to no more than 15 `$expand` options in a query. This is to protect performance. Each `$expand` options creates a join that can impact performance. 
 >  - To retrieve related entities for an entity instance, see [Retrieve related tables for a table by expanding navigation properties](retrieve-entity-using-web-api.md#bkmk_expandRelated). 
 > - Queries which expand collection-valued navigation properties may return cached data for those properties that doesn’t reflect recent changes. It is recommended to use `If-None-Match` header with value `null` to override browser caching. See [HTTP Headers](compose-http-requests-handle-errors.md#bkmk_headers) for more details.
 > 
@@ -130,7 +130,7 @@ OData-Version: 4.0
 You can expand single-valued navigation properties to multiple levels by nesting an `$expand` option within another `$expand` option.
 
 > [!NOTE]
-> There is no limit on the depth of nested `$expand` options, but the combined limit of 10 total `$expand` options in a query still applies.
+> There is no limit on the depth of nested `$expand` options, but the combined limit of 15 total `$expand` options in a query still applies.
 
 The following query returns `task` records and expands the related `contact`, the `account` related to the `contact`, and finally to the `systemuser` who created the  `account` record.
 
diff --git a/powerapps-docs/developer/model-driven-apps/clientapi/navigate-to-custom-page-examples.md b/powerapps-docs/developer/model-driven-apps/clientapi/navigate-to-custom-page-examples.md
@@ -26,9 +26,7 @@ This article provides examples of navigating from a model-driven app page to a c
 This article outlines the steps to use client API to open a custom page as a full-page, dialog, or pane.  It provides examples of **custom** as a `pageType` value in [navigateTo (Client API reference)](reference/xrm-navigation/navigateto.md).
 
 > [!IMPORTANT]
-> - The base functionality of custom pages has moved to general availability in all regions.  However some specific or new capabilities are still in public preview and are marked with _(preview)_.
-> - [!INCLUDE[cc_preview_features_definition](../../../includes/cc-preview-features-definition.md)] 
-> - Custom pages are a new feature with significant product changes and currently have a number of known limitations outlined in [Custom Page Known Issues](../../../maker/model-driven-apps/model-app-page-issues.md).
+> Custom pages are a new feature with significant product changes and currently have a number of known limitations outlined in [Custom Page Known Issues](../../../maker/model-driven-apps/model-app-page-issues.md).
 
 ## Navigating from a model page to a custom page
 
diff --git a/powerapps-docs/maker/TOC.yml b/powerapps-docs/maker/TOC.yml
@@ -1278,7 +1278,7 @@
           href: ./model-driven-apps/create-remove-pages.md
         - name: Manage app properties
           href: ./model-driven-apps/app-properties.md         
-        - name: Use custom pages within model-driven apps (preview)
+        - name: Use custom pages within model-driven apps
           items:
           - name: Custom pages overview
             href: ./model-driven-apps/model-app-page-overview.md
diff --git a/powerapps-docs/maker/model-driven-apps/add-page-to-model-app.md b/powerapps-docs/maker/model-driven-apps/add-page-to-model-app.md
@@ -1,7 +1,7 @@
 ---
 title: "Add a custom page to your model-driven app" 
 description: " Learn how to add a custom page to a model-driven app"
-ms.date: 06/29/2021
+ms.date: 05/26/2022
 ms.reviewer: "matp"
 
 ms.subservice: mda-maker
@@ -14,16 +14,14 @@ search.audienceType:
 search.app: 
   - "PowerApps"
 ---
-# Add a custom page to your model-driven app (preview)
+# Add a custom page to your model-driven app
 
 [!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
 
 This article guides you through creating and editing a custom page for a model-driven app using the modern app designer.
 
 > [!IMPORTANT]
-> - The base functionality of custom pages has moved to general availability in all regions.  However some specific or new capabilities are still in public preview and are marked with _(preview)_.
-> - [!INCLUDE[cc_preview_features_definition](../../includes/cc-preview-features-definition.md)] 
-> - Custom pages are a new feature with significant product changes and currently have a number of known limitations outlined in [Custom Page Known Issues](model-app-page-issues.md).
+> Custom pages are a new feature with significant product changes and currently have a number of known limitations outlined in [Custom Page Known Issues](model-app-page-issues.md).
 
 ## Create or edit a model-driven app using modern app designer
 
diff --git a/powerapps-docs/maker/model-driven-apps/custom-page-localize.md b/powerapps-docs/maker/model-driven-apps/custom-page-localize.md
@@ -1,8 +1,8 @@
 ---
-title: "Localize labels and strings on a custom page (preview)" 
+title: "Localize labels and strings on a custom page" 
 description: "This article outlines how to load resx files with localized content and how to use PowerFx to set content for labels on your custom page."
 ms.custom: ""
-ms.date: 11/01/2021
+ms.date: 05/26/2022
 ms.reviewer: ""
 
 ms.subservice: mda-maker
@@ -16,18 +16,14 @@ search.app:
   - "PowerApps"
   - D365CE
 ---
-# Localize labels, messages, and tooltips on a custom page (preview)
+# Localize labels, messages, and tooltips on a custom page
 
 [!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
 
 This article outlines how to add localized content to a custom page by uploading [web resource RESX](/powerapps/developer/model-driven-apps/resx-web-resources) files for each language into your solution. 
 
 This article shows you how to use Power Fx to set the content of a control on a custom page. You can use similar steps for tooltips and any messages that use a text control on the custom page.
 
-  > [!IMPORTANT]
-  > - This is a preview feature, and isn't available in all regions.
-  > - [!INCLUDE[cc_preview_features_definition](../../includes/cc-preview-features-definition.md)]
-
 ## Localizing labels on a custom page
 
 Providing localized content on a custom page in a model-driven app is vital when building apps that support global users or a multilingual organization. Translation can be done by uploading text files in a .resx format as a web resource. The files contain the translated text that you want to use for labels on your custom pages.
diff --git a/powerapps-docs/maker/model-driven-apps/design-page-for-model-app.md b/powerapps-docs/maker/model-driven-apps/design-page-for-model-app.md
@@ -2,7 +2,7 @@
 title: "Design a custom page for your model-driven app" 
 description: "Learn how to design a custom page for your model-driven app"
 ms.custom: ""
-ms.date: 07/21/2021
+ms.date: 05/26/2022
 ms.reviewer: ""
 
 ms.subservice: mda-maker
@@ -16,14 +16,12 @@ search.app:
   - PowerApps
   - D365CE
 ---
-# Design a custom page for your model-driven app (preview)
+# Design a custom page for your model-driven app
 
 This article provides tips for designing a custom page for use in a model-driven app.
 
 > [!IMPORTANT]
-> - The base functionality of custom pages has moved to general availability in all regions.  However some specific or new capabilities are still in public preview and are marked with _(preview)_.
-> - [!INCLUDE[cc_preview_features_definition](../../includes/cc-preview-features-definition.md)] 
-> - Custom pages are a new feature with significant product changes and currently have a number of known limitations outlined in [Custom Page Known Issues](model-app-page-issues.md).
+> Custom pages are a new feature with significant product changes and currently have a number of known limitations outlined in [Custom Page Known Issues](model-app-page-issues.md).
 
 ## Supported controls in a custom page
 
diff --git a/powerapps-docs/maker/model-driven-apps/model-app-page-issues.md b/powerapps-docs/maker/model-driven-apps/model-app-page-issues.md
@@ -2,7 +2,7 @@
 title: "Known issues with custom pages in a model-driven app"
 description: "Find the known issue that might occur when you create a custom page" 
 ms.custom: ""
-ms.date: 09/02/2021
+ms.date: 05/26/2022
 ms.reviewer: ""
 ms.subservice: mda-maker
 ms.topic: "article"
@@ -19,10 +19,6 @@ search.app:
 
 The custom page is a new page type within model-driven apps. Custom pages bring the power of canvas apps into model-driven apps. Below are the known issues to be aware of.
 
-> [!IMPORTANT]
-> - The base functionality of custom pages has moved to general availability in all regions.  However there are some specific or new capabilities that are still in public preview and are marked with _(preview)_.
-> - [!INCLUDE[cc_preview_features_definition](../../includes/cc-preview-features-definition.md)] 
-
 ## Maker-related issues
 
 * When a custom page is modified, such as saved and published, the model-driven app isn't aware of the change. The model-driven app will continue to use the last version of the custom page when the model-driven app was published. A model-driven app published through app designer, solution explorer, or **Publish all** will update all custom pages in the model-driven app.
diff --git a/powerapps-docs/maker/model-driven-apps/model-app-page-overview.md b/powerapps-docs/maker/model-driven-apps/model-app-page-overview.md
@@ -1,7 +1,7 @@
 ---
 title: "Converge model-driven and canvas apps using the custom page"
 description: "Add a custom page to use canvas as a page in your model-driven app" 
-ms.date: 06/20/2021
+ms.date: 05/26/2022
 ms.reviewer: "matp"
 
 ms.subservice: mda-maker
@@ -21,9 +21,7 @@ The custom page is a new page type within a model-driven app, which brings the p
 This new page can be more flexible than a model-driven app form, view, or dashboard page. It lets you include one or more tables. Then, the maker can define the data and component interactions. The custom page is a separate solution element, which allows one maker to edit one custom page at a time. Like other model-driven app pages, the page state is either from the parameters passed or retrieved from persisted tables.
 
 > [!IMPORTANT]
-> - The base functionality of custom pages has moved to general availability in all regions.  However some specific or new capabilities are still in public preview and are marked with _(preview)_.
-> - [!INCLUDE[cc_preview_features_definition](../../includes/cc-preview-features-definition.md)] 
-> - Custom pages are a new feature with significant product changes and currently have a number of known limitations outlined in [Custom Page Known Issues](model-app-page-issues.md).
+> Custom pages are a new feature with significant product changes and currently have a number of known limitations outlined in [Custom Page Known Issues](model-app-page-issues.md).
 
 | Capability | Status | Notes |
 | -- | -- | -- |
@@ -33,10 +31,10 @@ This new page can be more flexible than a model-driven app form, view, or dashbo
 | Modern controls in custom pages | General Availability | [List of supported controls](design-page-for-model-app.md#supported-controls-in-a-custom-page)
 | Code components in custom pages | General Availability |
 | Monitor support for custom pages | General Availability |
-| Authoring custom pages | Public Preview | Modern app designer and canvas designer are expected to be used to author custom page that are supported at runtime |
-| Canvas components in custom pages | Public Preview |
-| Custom page in Teams model-driven app | Public Preview |
-| Custom page in mobile online | Public Preview | iOS must allow enabling “Allow cross site tracking” that can be prevented by device management |
+| Authoring custom pages | General Availability | Modern app designer and canvas designer are expected to be used to author custom page that are supported at runtime |
+| Canvas components in custom pages | General Availability |
+| Custom page in Teams model-driven app | General Availability |
+| Custom page in mobile online | General Availability | iOS must allow enabling “Allow cross site tracking” that can be prevented by device management |
 
 ## Examples of custom pages
 
diff --git a/powerapps-docs/maker/model-driven-apps/page-code-components.md b/powerapps-docs/maker/model-driven-apps/page-code-components.md
@@ -2,7 +2,7 @@
 title: "Add code components to a custom page for your model-driven app" 
 description: "This article outlines the use of code components built by professional developers using the Power Apps component framework within a custom page."
 ms.custom: ""
-ms.date: 07/14/2021
+ms.date: 05/26/2022
 ms.reviewer: ""
 
 ms.topic: "article"
diff --git a/powerapps-docs/maker/model-driven-apps/page-powerfx-in-model-app.md b/powerapps-docs/maker/model-driven-apps/page-powerfx-in-model-app.md
@@ -2,7 +2,7 @@
 title: "Use Power Fx in custom page for your model-driven app" 
 description: "This article outlines how the common Microsoft Power FX functions work within a custom page."
 ms.custom: ""
-ms.date: 07/06/2021
+ms.date: 05/26/2022
 ms.reviewer: ""
 
 ms.subservice: mda-maker
@@ -21,9 +21,7 @@ search.app:
 This article outlines how the common [Microsoft Power Fx](../canvas-apps/formula-reference.md) functions work differently between a standalone canvas apps and a custom page. This is because a custom page is a component within the model-driven app. Other Microsoft Power Fx formulas continue to behave in the same way.
 
 > [!IMPORTANT]
-> - The base functionality of custom pages has moved to general availability in all regions.  However some specific capabilities or new capabilities are still in public preview and are marked with _(preview)_.
-> - [!INCLUDE[cc_preview_features_definition](../../includes/cc-preview-features-definition.md)] 
-> - Custom pages are a new feature with significant product changes and currently have a number of known limitations outlined in [Custom Page Known Issues](model-app-page-issues.md).
+> Custom pages are a new feature with significant product changes and currently have a number of known limitations outlined in [Custom Page Known Issues](model-app-page-issues.md).
 
 ## Add notifications to a custom page
 
@@ -83,7 +81,7 @@ To navigate to the default form of the table, pass the record as the first param
 Navigate( Gallery1.Selected )
 ```
 
-### Navigate to a specific form of a table (preview)
+### Navigate to a specific form of a table
 
 To pass a Dataverse record to a specific form, pass the form name in the second parameter's Page attribute.
 
@@ -93,7 +91,7 @@ Navigate(
   { Page: 'Accounts (Forms)'.Account  } )
 ```
 
-### Navigate to a specific custom page with a record input (preview)
+### Navigate to a specific custom page with a record input
 
 To pass a Dataverse record to a specific custom page, pass the custom page name in the second parameter's Page attribute.
 
@@ -121,7 +119,7 @@ To navigate to the default form of the table in create mode, pass a Dataverse re
 Navigate( Defaults( Accounts ) )
 ```
 
-### Navigate to the default form of the table in create mode with field defaulted (preview)
+### Navigate to the default form of the table in create mode with field defaulted
 
 To navigate to a new record with some fields defaulted, use **Patch** function to set fields on the default record for the table. 
 
diff --git a/powerapps-docs/maker/portals/configure/enable-multiple-language-support.md b/powerapps-docs/maker/portals/configure/enable-multiple-language-support.md
@@ -5,7 +5,7 @@ author: sandhangitmsft
 
 ms.topic: conceptual
 ms.custom: 
-ms.date: 12/17/2021
+ms.date: 06/03/2022
 ms.subservice: portals
 ms.author: sandhan
 ms.reviewer: ndoelman
@@ -47,10 +47,14 @@ You can set the default language of your portal by changing the *Default Languag
 
 ## Supported languages
 
-The table below shows all the languages currently available out of the box. This list can be found by going to **Portals** &gt; **Content** &gt; **Portal Languages**. The Portal Display Name of a language can be changed after selecting the language to change from this page. Note that the list now includes East Asian languages (Japanese, Chinese, and Korean).
+The table below shows all the languages currently available out of the box. This list can be found by going to **Portals** &gt; **Content** &gt; **Portal Languages**. The Portal Display Name of a language can be changed after selecting the language to change from this page.
+
+> [!NOTE]
+> Upgrade your portals website version to [9.4.4.xx](/power-platform/released-versions/portals/portalupdate944x) and package version [9.3.2204](../admin/update-portal-solution.md) to configure Arabic and Hebrew language for your website.
 
 | **Name**                           | **Language Code** | **LCID** | **Portal Display Name** |
 |------------------------------------|-------------------|----------|-------------------------|
+| Arabic                             | ar-SA             | 1025     | عربي                    |
 | Basque - Basque                    | eu-ES             | 1069     | euskara                 |
 | Bulgarian - Bulgaria               | bg-BG             | 1026     | български               |
 | Catalan - Catalan                  | ca-ES             | 1027     | català                  |
@@ -68,6 +72,7 @@ The table below shows all the languages currently available out of the box. This
 | Galician - Spain                   | gl-ES             | 1110     | galego                  |
 | German - Germany                   | de-DE             | 1031     | Deutsch                 |
 | Greek - Greece                     | el-GR             | 1032     | Ελληνικά                |
+| Hebrew                             | he-IL             | 1037     | עִברִית                 |  
 | Hindi - India                      | hi-IN             | 1081     | हिंदी                   |
 | Hungarian - Hungary                | hu-HU             | 1038     | magyar                  |
 | Indonesian - Indonesia             | id-ID             | 1057     | Bahasa Indonesia        |
@@ -128,4 +133,3 @@ To avoid choosing the language from the drop down each time, Portal users can se
 > [!Note]
 > You will need to configure [table permissions](assign-entity-permissions.md) on the portal language table (adx_portallanguage) to allow read and append access linked to the default authenticated user web role to allow for users to choose their default language.
 
-[!INCLUDE[footer-include](../../../includes/footer-banner.md)]
