Merge branch 'main' into noazarur_moderncontroldocupdates

Author: noazarur-microsoft

.openpublishing.redirection.json

@@ -1,5 +1,20 @@
 {
   "redirections": [
+   {
+      "source_path": "powerapps-docs/developer/data-platform/webapi/setup-postman-environment.md",
+      "redirect_url": "insomnia",
+      "redirect_document_id": "false"
+   },
+   {
+      "source_path": "powerapps-docs/developer/data-platform/webapi/use-postman-perform-operations.md",
+      "redirect_url": "insomnia",
+      "redirect_document_id": "false"
+   },
+   {
+      "source_path": "powerapps-docs/developer/data-platform/webapi/use-postman-web-api.md",
+      "redirect_url": "insomnia",
+      "redirect_document_id": "false"
+   },   
    {
       "source_path": "powerapps-docs/developer/data-platform/upsertmultiple.md",
       "redirect_url": "bulk-operations#upsertmultiple",
@@ -8825,6 +8840,51 @@
       "redirect_url": "/power-pages/",
       "redirect_document_id": false
     },
+    {
+      "source_path": "powerapps-docs/maker/canvas-apps/add-scrolling-screen.md",
+      "redirect_url": "/power-apps/maker/canvas-apps/add-screen-context-variables",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "powerapps-docs/maker/canvas-apps/screen-templates/calendar-screen-overview.md",
+      "redirect_url": "/power-apps/maker/canvas-apps/add-screen-context-variables",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "powerapps-docs/maker/canvas-apps/screen-templates/calendar-screen-reference.md",
+      "redirect_url": "/power-apps/maker/canvas-apps/add-screen-context-variables",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "powerapps-docs/maker/canvas-apps/screen-templates/email-screen-overview.md",
+      "redirect_url": "/power-apps/maker/canvas-apps/add-screen-context-variables",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "powerapps-docs/maker/canvas-apps/screen-templates/email-screen-reference.md",
+      "redirect_url": "/power-apps/maker/canvas-apps/add-screen-context-variables",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "powerapps-docs/maker/canvas-apps/screen-templates/meeting-screen-overview.md",
+      "redirect_url": "/power-apps/maker/canvas-apps/add-screen-context-variables",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "powerapps-docs/maker/canvas-apps/screen-templates/meeting-screen-reference.md",
+      "redirect_url": "/power-apps/maker/canvas-apps/add-screen-context-variables",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "powerapps-docs/maker/canvas-apps/screen-templates/people-screen-overview.md",
+      "redirect_url": "/power-apps/maker/canvas-apps/add-screen-context-variables",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "powerapps-docs/maker/canvas-apps/screen-templates/people-screen-reference.md",
+      "redirect_url": "/power-apps/maker/canvas-apps/add-screen-context-variables",
+      "redirect_document_id": false
+    },
     {
       "source_path": "powerapps-docs/maker/portals/terminology-changes.md",
       "redirect_url": "/power-pages/configure/design-build-overview",
@@ -8934,6 +8994,11 @@
       "source_path": "powerapps-docs/maker/portals/legacy-portal-faq.yml",
       "redirect_url": "/power-pages/configure/design-build-overview",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "powerapps-docs/maker/data-platform/table-settings-for-copilot.md",
+      "redirect_url": "/power-apps/maker/model-driven-apps/add-ai-copilot",
+      "redirect_document_id": false
     }
   ]
 }

powerapps-docs/developer/component-framework/custom-controls-overview.md

@@ -13,7 +13,7 @@ contributors:
 
 # Code components
 
-Code components are a type of solution component, which means they can be included in a solution file and imported into different environments. More information: [Package and distribute extensions using solutions](/dynamics365/customer-engagement/developer/package-distribute-extensions-use-solutions).
+Code components are a type of solution component, which means they can be included in a solution file and imported into different environments. [Learn how to package and distribute extensions using solutions](/power-platform/alm/solution-concepts-alm).
 
 [!INCLUDE[cc-terminology](../data-platform/includes/cc-terminology.md)]
 

powerapps-docs/developer/component-framework/debugging-custom-controls.md

@@ -241,7 +241,7 @@ To debug your code component using Fiddler:
    > [!div class="mx-imgBorder"] 
    > ![AutoResponder rule.](media/fiddler-rule-example.png "AutoResponder rule")
 
-   If you want a simpler **AutoResponder** rule approach, see [Streamline JavaScript web resource development using Fiddler AutoResponder](/dynamics365/customer-engagement/developer/streamline-javascript-development-fiddler-autoresponder).
+   If you want a simpler **AutoResponder** rule approach, see [Script web resource development using Fiddler AutoResponder](../model-driven-apps/streamline-javascript-development-fiddler-autoresponder.md).
 
 8. Enter the following for the path to respond with:
 

powerapps-docs/developer/component-framework/reference/utility/lookupobjects.md

@@ -3,12 +3,13 @@ title: lookupObjects (Power Apps component framework API reference) | Microsoft
 description: Opens a lookup dialog allowing the user to select one or more items.
 ms.author: hemantg
 author: HemantGaur
-ms.date: 05/27/2022
+ms.date: 03/01/2024
 ms.reviewer: jdaly
 ms.topic: reference
 ms.subservice: pcf
 contributors:
  - JimDaly
+ - rarattay
 ---
 
 # lookupObjects
@@ -27,12 +28,31 @@ Model-driven apps
 
 | Parameter Name|Type|Required|Description|
 | ------------- |----|--------|-----------|
-|lookupOptions|`UtilityApi.LookupOptions`|Yes|Defines the options for opening the lookup dialog. For a list of lookupOptions, see [lookupOptions](../../../model-driven-apps/clientapi/reference/Xrm-Utility/lookupObjects.md) |
+|lookupOptions|`UtilityApi.LookupOptions`|Yes|Defines the options for opening the lookup dialog. See [Remarks](#remarks) |
 
 ## Return Value
 
 Type: Promise<LookupValue[]>
 
+## Remarks
+
+The lookupOptions available for components is different from those for the [Client API Xrm.Utility.lookupObjects lookupOptions properties](../../../model-driven-apps/clientapi/reference/Xrm-Utility/lookupObjects.md#lookupoptions-properties) available for model-driven app client side scripts.
+
+### lookupOptions properties
+
+For components, lookupOptions parameter has the following properties:
+
+|Property Name |Type |Required |Description |
+|---|---|---|---|
+|`allowMultiSelect`|Boolean|No|Indicates whether the lookup allows more than one item to be selected.|
+|`defaultEntityType`|String|No|The default table type to use.|
+|`defaultViewId`|String|No|The default view to use.|
+|`entityTypes`|Array|Yes|The table types to display.|
+|`searchText`|String|No|Indicates the default search term for the lookup control. This is supported only on [Unified Interface](/power-platform/admin/about-unified-interface).|
+|`viewIds`|Array|No|The views to be available in the view picker. Only system views are supported.|
+
+The `disableMru` and `filters` properties available for model-driven app client scripts are not available for components.
+
 
 ### Related articles
 

powerapps-docs/developer/component-framework/sample-controls/localization-api-control.md

@@ -20,7 +20,7 @@ This sample showcases how localization is done for code components. In this samp
 > [!NOTE]
 > Code component runtime localization is in Public Preview for Custom page and Canvas applications. More information: [Blog: Runtime localization support for Code components on Custom pages and Canvas apps](https://powerapps.microsoft.com/en-us/blog/runtime-localization-support-for-code-components-on-custom-pages-and-canvas-apps/). 
 
-Power Apps component framework uses the concept of implementing String(resx) web resources that is used to manage the localized strings shown on any user interface. More information: [String(Resx) Web resources](/dynamics365/customer-engagement/developer/resx-web-resources). 
+Power Apps component framework uses the concept of implementing String(resx) web resources that is used to manage the localized strings shown on any user interface. More information: [RESX web resources](../../model-driven-apps/resx-web-resources.md). 
 > [!div class="mx-imgBorder"]
 > ![Localization API component.](../media/localization-api-control.png "Localization API component")
 

powerapps-docs/developer/component-framework/sample-controls/navigation-api-control.md

@@ -35,28 +35,28 @@ The `openAlertDialog` method provides the capability to display an alert dialog
 In this sample when you click on the `openAlertDialogButton` an alert dialog pops up and sets the value of it to `Alert dialog closed` when the dialog is closed either using the `OK` button or the `X` button.
 
 > [!NOTE]
-> This is similar to calling the [Xrm.Navigation.openAlertDialog](/dynamics365/customer-engagement/developer/clientapi/reference/xrm-navigation/openalertdialog) method in ClientAPI.  
+> This is similar to calling the [Xrm.Navigation.openAlertDialog](../../model-driven-apps/clientapi/reference/Xrm-Navigation/openAlertDialog.md) method in ClientAPI.  
 
 The `openConfirmDialog` method provides the ability to display an alert dialog containing a message and two buttons. You can use this method to implement different logic based on the button clicked. You can implement the success callback which is called when the dialog is closed by clicking either of the buttons.
 
 This sample shows you a confirm dialog when you click on the `openConfirmDialogButton` and sets the value of it to `Ok` or `Cancel`, or `X` depending on the button that was clicked.
 
 > [!NOTE]
-> This is similar to calling the [Xrm.Navigation.openConfirmDialog](/dynamics365/customer-engagement/developer/clientapi/reference/xrm-navigation/openconfirmdialog) method in ClientAPI.
+> This is similar to calling the [Xrm.Navigation.openConfirmDialog](../../model-driven-apps/clientapi/reference/Xrm-Navigation/openConfirmDialog.md) method in ClientAPI.
   
 The `openFile` method provides the ability to open a file. You'd need to pass in the file object which has the filename, content, mimetype and the filesize. You can also pass in the optional parameter of the mode you want to open the file as 1 or 2, 1 being the default which opens the file in read or open mode.
 
 This sample opens a file named `SampleDemo.txt` in save mode on clicking the `openFileButton`.
 
 > [!NOTE]
-> This is similar to calling the [Xrm.Navigation.openFile](/dynamics365/customer-engagement/developer/clientapi/reference/xrm-navigation/openfile) method in ClientAPI.
+> This is similar to calling the [Xrm.Navigation.openFile](../../model-driven-apps/clientapi/reference/Xrm-Navigation/openFile.md) method in ClientAPI.
 
 The `openUrl` method provides the ability to open a URL. You need to pass the URL as a string to the method and also pass the optional parameters of height, width and openInNewWindow as true if you want the URL to be opened in a new window.
 
 This sample opens a new window and loads the microsoft.com home page on clicking the `openUrlButton`.
 
 > [!NOTE]
-> This is similar to calling the [Xrm.Navigation.openUrl](/dynamics365/customer-engagement/developer/clientapi/reference/xrm-navigation/openurl) method in ClientAPI.
+> This is similar to calling the [Xrm.Navigation.openUrl](../../model-driven-apps/clientapi/reference/Xrm-Navigation/openUrl.md) method in ClientAPI.
 
 ### Related topics
 

powerapps-docs/developer/data-platform/aad-group-team.md

@@ -55,7 +55,7 @@ Accept: application/json
 
 Where:
 
-- Membership type is defined in the [team property](/dynamics365/customer-engagement/web-api/team#properties) `membershiptype`
+- Membership type is defined in the [Team table MembershipType column](reference/entities/team.md#BKMK_MembershipType)
 - Name of the team is the name of the Microsoft Entra ID group
 - Team type is based on the Microsoft Entra ID group type - for example "Security" or "Microsoft 365"
 
@@ -242,7 +242,7 @@ GET [Organization URI]/api/data/v9.0/RetrieveAadUserPrivileges(DirectoryObjectId
 
 ## Checking user or team's access rights on a record
 
-If you have a non-interactive process where your service needs to check if the user has access rights to a record, you can make a [RetrievePrincipalAccess function](/dynamics365/customer-engagement/web-api/retrieveprincipalaccess) call on behalf of the user by specifying the `CallerID`.
+If you have a non-interactive process where your service needs to check if the user has access rights to a record, you can make a [RetrievePrincipalAccess function](xref:Microsoft.Dynamics.CRM.RetrievePrincipalAccess) call on behalf of the user by specifying the `CallerID`.
 
 More information: [Impersonate another user](impersonate-another-user.md)
 

powerapps-docs/developer/data-platform/add-transformation-mappings-import.md

@@ -175,7 +175,7 @@ Returns a substring of a specified length, starting at a specified point in the
 |Input Parameters|Description|  
 |----------------------|-----------------|  
 |Year Offset|Positive or negative value that is added to the year component of a current date or absolute year.|  
-|Year Offset Mode|Specify whether the offset is relative to the current date or absolute value by using the `TransformationParameterMapping.Data` column. If you are using early bound types, you can use the `TransformationOffsetMode` enumeration to specify relative or absolute offset. For a list of the DataTypeCode values, see the choice values for this table. To view the metadata for your organization, install the Metadata Browser solution described in [Browse the metadata for your organization](/dynamics365/customer-engagement/developer/browse-your-metadata). You can also browse the reference documentation for tables in the [Table Reference](/dynamics365/customer-engagement/developer/about-entity-reference).  
+|Year Offset Mode|Specify whether the offset is relative to the current date or absolute value by using the `TransformationParameterMapping.Data` column. If you are using early bound types, you can use the `TransformationOffsetMode` enumeration to specify relative or absolute offset. For a list of the DataTypeCode values, see the choice values for this table. To view the metadata for your organization, install the Metadata Browser solution described in [Browse table definitions in your environment](browse-your-metadata.md). You can also browse the reference documentation for tables in the [Dataverse table/entity reference](reference/about-entity-reference.md).  
 |Month Offset|Positive or negative value that is added to the month component of a current date or absolute month.|  
 |Month Offset Mode|Specify whether the offset is relative to the current date or absolute value by using the `TransformationParameterMapping.Data` column. If you are using early bound types, you can use the `TransformationOffsetMode` enumeration to specify relative or absolute offset. For a list of the DataTypeCode values, see the choice values for this table.|  
 |Day Offset|Positive or negative value that is added to the day component of a current date or absolute day.|  

powerapps-docs/developer/data-platform/configure-data-import.md

@@ -16,7 +16,7 @@ The configuration information that is required for importing data is contained i
 
  To configure data import, do the following:  
 
-- Use the `Import.ModeCode` column to specify whether to create or update data during import. If you are using early bound types, you can use the `ImportModeCode` enumeration. For a list of the ModeCode values, see the choice values for this table. To view the metadata for your organization, install the Metadata Browser solution described in [Browse the metadata for your organization](/dynamics365/customer-engagement/developer/browse-your-metadata). You can also browse the reference documentation for tables in the [Table Reference](/dynamics365/customer-engagement/developer/about-entity-reference).  
+- Use the `Import.ModeCode` column to specify whether to create or update data during import. If you are using early bound types, you can use the `ImportModeCode` enumeration. For a list of the ModeCode values, see the choice values for this table. To view the metadata for your organization, install the Metadata Browser solution described in [Browse table definitions in your environment](browse-your-metadata.md). You can also browse the reference documentation for tables in the [Dataverse table/entity reference](reference/about-entity-reference.md).  
 - Use the `ImportFile.FileTypeCode` column to specify the type of the import file. If you are using early bound types, you can use the `ImportFileType` enumeration. For a list of the FileTypeCode values, see the choice values for this table.  
 - Use the `ImportFile.DataDelimiterCode` column to specify the single character data delimiter in the import file. If you are using early bound types, you can use the `ImportDataDelimiter` enumeration. For a list of the ImportDataDelimiter values, see the choice values for this table.  
 - Use the `ImportFile.FieldDelimiterCode` column to specify the single character column delimiter in the import file. If you are using early bound types, you can use the `ImportFieldDelimiter` enumeration. For a list of the FieldDelimiterCode values, see the choice values for this table.  

powerapps-docs/developer/data-platform/configure-exchange-folder-level-tracking-rules.md

@@ -16,7 +16,7 @@ search.audienceType:
 
 Configure folder-level tracking rules to map a Microsoft Exchange inbox folder to a Microsoft Dataverse record so that all the emails in the Microsoft Exchange folder get automatically tracked against the mapped record in Dataverse. Folder-level tracking of emails will work only if:  
 
-- The folder-level tracking feature is enabled for your Dataverse instance. You can enable folder-level tracking by using the web client or Dynamics 365 for Outlook. More information: [Configure folder-level tracking](/dynamics365/customer-engagement/admin/configure-outlook-exchange-folder-level-tracking)  
+- The folder-level tracking feature is enabled for your Dataverse instance. You can enable folder-level tracking by using the web client or Dynamics 365 for Outlook. More information: [Configure folder-level tracking](/power-platform/admin/configure-outlook-exchange-folder-level-tracking)  
 
 - The folder that you are tracking is under the **Inbox** folder in Microsoft Exchange. Emails in the folders that are not under the **Inbox** folder won't be tracked.  
 
@@ -88,7 +88,7 @@ foreach (var folderMapping in resp.MailboxTrackingFolderMappings)
  <xref:Microsoft.Dynamics.CRM.RetrieveMailboxTrackingFolders?text=RetrieveMailboxTrackingFolders Function><br />
  [Mailbox Auto Tracking Folder (MailboxTrackingFolder)  table](reference/entities/mailboxtrackingfolder.md)<br />
  [Mailbox table](reference/entities/mailbox.md)<br />
- [Configure folder-level tracking](/dynamics365/customer-engagement/admin/configure-outlook-exchange-folder-level-tracking)<br />
+ [Configure folder-level tracking](/power-platform/admin/configure-outlook-exchange-folder-level-tracking)<br />
  [Server-side Synchronization tables](server-side-synchronization-entities.md)<br />