Live publish

Author: buck1ey

powerapps-docs/developer/data-platform/webapi/query-metadata-web-api.md

@@ -1,7 +1,7 @@
 ---
 title: "Query table definitions using the Web API (Microsoft Dataverse) | Microsoft Docs"
 description: "The capability to query table definitions (metadata) is available using the Web API and using the Organization service by using RetrieveMetadataChangesRequest"
-ms.date: 01/11/2023
+ms.date: 03/01/2023
 ms.topic: article
 applies_to: 
   - "Dynamics 365 (online)"
@@ -82,6 +82,14 @@ You can use any of the `EntityMetadata` properties with `$select` system query o
 
 There are no limits on the number of metadata entities that will be returned in a query. There's no paging. All matching resources will be returned in the first response.  
 
+## Limit languages returned
+
+When an environment has many languages provisioned, the amount of data returned can grow large. For best performance, limit the language labels returned using the `LabelLanguages` parameter with the LCID value of the language you want to return.
+
+[!INCLUDE [languagecode](../../../includes/languagecode.md)]
+
+For example, appending the following will limit the localized language labels to English: `&LabelLanguages=1033`.
+
 <a name="bkmk_filterEnumTypes"></a>
 
 ## Use enum types in $filter operations

powerapps-docs/maker/TOC.yml

@@ -2283,11 +2283,11 @@
         - name: Integrate Field Service
           href: ./portals/customer-engagement-apps/integrate-field-service.md
     - name: Important upcoming changes and deprecations
-      href: ./portals/important-changes-deprecations.md
+      href: /power-pages/important-changes-deprecations
     - name: Known issues
       href: /power-pages/known-issues
     - name: Power Apps portals FAQs
-      href: ./portals/faq.yml
+      href: /power-pages/faq
     - name: Legacy Adxstudio Portals v7 FAQs
       href: ./portals/legacy-portal-faq.yml
     - name: Version releases and updates

powerapps-docs/maker/portals/configure/entity-forms.md

@@ -226,7 +226,6 @@ To disable request validation, follow these steps:
 - The Connection table subgrids aren't supported in basic forms. If you add a Connection table subgrid to the form using Form designer, error messages are displayed when you render the form on the portal and use the Connection table.
 - Duplicate fields, Party List fields, and business rules aren't supported in basic forms.
 - Field level code components are in public preview, and can be added to forms. More information: [Add a code component to a field in a model-driven app](../component-framework.md#add-a-code-component-to-a-field-in-a-model-driven-app) 
-- [Image attributes](../../../developer/data-platform/image-attributes.md), [file attributes](../../../developer/data-platform/file-attributes.md) and [table images](/dynamics365/customerengagement/on-premises/developer/sample-set-retrieve-entity-images) aren't supported in [basic forms](entity-forms.md), [multistep forms](web-form-properties.md) or when using liquid template tags, such as [fetchxl](../liquid/template-tags.md).
 - Business rules and client API can enable locked fields on a read-only form.
 - If you create a basic form in the Insert mode, you can't change a button's alignment or place an action button above the basic form.
 - If you render a lookup control as a dropdown list on the form, the related records filter does not work.