Merge branch 'main' into ewehrle-TOC-edit

Author: tapanm-MSFT

.openpublishing.publish.config.json

@@ -67,10 +67,7 @@
       "path_to_root": "PowerApps-Samples",
       "url": "https://github.com/microsoft/PowerApps-Samples",
       "branch": "master",
-      "branch_mapping": {
-        "master": "master",
-        "live": "master"
-      }
+      "branch_mapping": {}
     },
     {
       "path_to_root": "shared-content",

.openpublishing.redirection.json

@@ -1,5 +1,15 @@
 {
   "redirections": [
+   {
+      "source_path": "powerapps-docs/developer/data-platform/org-service/extend-code-generation-tool.md",
+      "redirect_url": "/dynamics365/customerengagement/on-premises/developer/org-service/extend-code-generation-tool",
+      "redirect_document_id": "false"
+   },
+   {
+    "source_path": "powerapps-docs/developer/data-platform/dependent-assembly-plugins.md",
+    "redirect_url": "build-and-package",
+    "redirect_document_id": "false"
+   },
    {
       "source_path": "powerapps-docs/developer/model-driven-apps/clientapi/reference/composite-attributes.md",
       "redirect_url": "/previous-versions/dynamicscrm-2016/developers-guide/dn481581(v=crm.8)",
@@ -470,6 +480,16 @@
       "redirect_url": "/power-pages/configure/azure-front-door",
       "redirect_document_id": false
     },
+    {
+      "source_path": "powerapps-docs/developer/data-platform/search/index.md",
+      "redirect_url": "/powerapps/developer/data-platform/search/overview",
+      "redirect_document_id": "false"
+    },
+    {
+      "source_path": "powerapps-docs/developer/data-platform/webapi/relevance-search.md",
+      "redirect_url": "../search/overview.md",
+      "redirect_document_id": false
+    },
     {
       "source_path": "powerapps-docs/maker/portals/admin/portal-checker-analysis.md",
       "redirect_url": "/power-apps/maker/portals/admin/portal-checker#next-steps",
@@ -8719,6 +8739,11 @@
       "source_path": "powerapps-docs/maker/portals/create-common-problems.md",
       "redirect_url": "/power-pages/getting-started/create-manage",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "powerapps-docs/maker/canvas-apps/working-with-dynamic-schema.md",
+      "redirect_url": "/power-apps/maker/canvas-apps/untyped-and-dynamic-objects#converting-formulas-that-return-untyped-objects-that-previously-returned-boolean",
+      "redirect_document_id": false
     }
   ]
 }

powerapps-docs/cards/manage-cards/delete-cards.md

@@ -13,7 +13,7 @@ ms.collection:
 
 # Delete a card
 
-To delete a card, you need to be the app owner. An administrator, such as Global admin, Azure Active Directory Global admin, or Dynamics 365 admin can't delete card.
+To delete a card, you need to be the app owner. An administrator, such as Global admin, Microsoft Entra Global admin, or Dynamics 365 admin can't delete card.
 
 1. Sign in to [Power Apps](https://make.powerapps.com).
 1. From the [left navigation](../../maker/canvas-apps/intro-maker-portal.md#1--left-navigation-pane), select **Cards**.  

powerapps-docs/cards/media/send-a-card/Send_card_to_a_Teams_user.png

@@ -1,5 +1,5 @@
 ---
-title: Send a card automatically with a flow (preview)
+title: Send a card automatically with a flow 
 description: Learn how to send a card automatically using a Power Automate flow.
 keywords: "Card Designer, Power Apps, cards, send a card, Power Automate, flow"
 author: anuitz
@@ -15,19 +15,21 @@ contributors:
   - anuitz
 ---
 
-# Send a card automatically with a flow (preview)
+# Send a card automatically with a flow 
 
-[!INCLUDE[cards_preview_notice](../includes/preview-include.md)]
+Use Power Automate to send cards for Power Apps from a flow. By setting up a flow that is triggered by an event, you can automate the process of sending cards in Teams. For instance, you can create a flow that requests the assigned individual to approve or reject an expense when a new record is added to Dataverse. Alternatively, you can create a flow that sends a daily status update in Teams every morning.
 
-Use Power Automate to send cards. By setting up a flow that is triggered by an event, you can automate the process of sending cards. For instance, you can create a flow that requests the assigned individual to approve or reject an expense when a new record is added to Dataverse. Alternatively, you can create a flow that sends a daily status update every morning.
+You can use **Send from a flow** option in **Send** menu on the card's **Play** page to launch a Power Automate flow template for sending cards in Teams. You can modify and save this template as a new flow to post your card in Teams chat or channel or send it to a specific Teams user.
+
+   :::image type="content" source="../media/send-a-card/Send_from_flow.png" alt-text="Select Send from flow option to lauch a Power Automate template.":::
 
 ## Prerequisites
 
 - [Power Automate](https://make.powerautomate.com) account
 - Create a [card](../tutorials/hello-world-card.md)
 - The [Power Apps Teams app](send-card-in-teams.md#add-power-apps-to-teams) installed in the chat, group chat, or channel that the card will be sent to
 
-## Cards for Power Apps connector
+## Use Cards for Power Apps connector in Power Automate
 
 The **Cards for Power Apps** connector is used to create instances of cards to send using a flow. The connector has no triggers and two actions:
 
@@ -36,20 +38,34 @@ The **Cards for Power Apps** connector is used to create instances of cards to s
 
    :::image type="content" source="../media/send-a-card/cards-connector.png" alt-text="Screenshot of the cards for Power Apps connector.":::
 
-## Send card in Teams using the Teams connector
+## Send a card for Power Apps in Teams chat or channel 
 
-Sending a card in Teams requires a card instance. To get a card instance, use the **Cards for Power Apps** connector actions. The **Create card instance** action has `Card` dynamic content that can be used with the **Teams** connector **Post card in a chat or channel** action.
+Sending a card in Teams froma  flow requires a card instance. To crearte a card instance, use the **Cards for Power Apps** connector actions. The **Create card instance** action has `Card` dynamic content that can be used with the **Teams** connector **Post card in a chat or channel** action.
 
-1. Create or modify an existing flow
+1. Create or modify an existing flow, or use **Send** > **Send from a flow** on cards for Power Apps **Play** page to start with a template.
 1. Make sure the flow has a trigger. In the screenshot below, the trigger is when a new account record is created.
-1. Create or get the card instance you want to send using the **Cards for Power Apps** connector. In the screenshot, we created a card instance of the `Account Card` and setting the `Body` input variable to the `Account Name` of the newly created account record.
+1. Create a card instance you want to send using the **Cards for Power Apps** connector's **Create card instance** action. In the screenshot, we created a card instance of the `Account Card` and setting the `Body` input variable to the `Account Name` of the newly created account record.
 1. Add an action to **Post card in a chat or channel** using the **Teams** connector.
-1. On the action, set **Post as** to `Power Apps (Preview)`.
+1. On the action, set **Post as** to `Power Apps`.
 1. On the action, set **Post in**, **Team** & **Channel**, or **Group chat** to the conversation you want to send the card in. In the example screenshot, this is to the `Cards for Power Apps (Customer Channel)` Teams in the `General` channel.
 1. On the action, set **Card** to the `Card` dynamic content from the **Cards for Power Apps** connector action you added earlier.
 
    :::image type="content" source="../media/send-a-card/card-in-flow-example.png" alt-text="Screenshot a flow that creates a card instance when an account record is created and sends it in Teams.":::
 
+## Send a card for Power Apps to a Teams user
+You can send a card to a specific Teams user. In a Power Automate flow, use the **Create card instance** action in **Cards for Power Apps** connector actions to create a card instance as `Card`  dynamic content. You can use the resulting `Card` dynamic content with the **Teams** connector **Post card in a chat or channel** action to send a card to a specific Teams user.
+
+1. Create or modify an existing flow, or use **Send** > **Send from a flow** on cards for Power Apps **Play** page to start with a template.
+1. Make sure the flow has a trigger. In the screenshot below, the trigger is when a new account record is created.
+1. Create a card instance you want to send using the **Cards for Power Apps** connector's **Create card instance** action. In the screenshot, we created a card instance of the `Account Card` and setting the `Body` input variable to the `Account Name` of the newly created account record.
+1. Add an action to **Post card in a chat or channel** using the **Teams** connector.
+1. On the action, set **Post as** to `Power Apps`.
+1. On the action, set **Post in** to **Chat with Power Apps**.
+1. On the action, enter the **Teams user** you want to post the card to.
+1. On the action, set **Card** to the `Card` dynamic content from the **Cards for Power Apps** connector action you added earlier.
+
+    :::image type="content" source="../media/send-a-card/Send_card_to_a_Teams_user.png" alt-text="Screenshot a flow that creates a card instance when an account record is created and sends it to a specific Teams user.":::
+
 ## Managing your flow in a solution
 
 For more details on managing your flow that uses the Card for Power Apps Connector, see [Manage cards in solutions](../manage-cards/manage-cards.md).

powerapps-docs/cards/media/send-a-card/Send_from_flow.png

@@ -1,8 +1,8 @@
 ---
 title: Add code components to a column or table in model-driven apps | Microsoft Docs
 description: Learn how to add code components to a column or table.
-ms.author: noazarur
-author: noazarur-microsoft
+ms.author: hemantg
+author: HemantGaur
 ms.date: 05/27/2022
 ms.reviewer: jdaly
 ms.topic: article

powerapps-docs/cards/send-a-card/send-card-with-flow.md

@@ -1,8 +1,8 @@
 ---
 title: "Code components application lifecycle management | MicrosoftDocs"
 description: "Learn about the considerations and strategies for working with specific aspects of ALM from the perspective of code components in Microsoft Dataverse."
-ms.author: noazarur
-author: noazarur-microsoft
+ms.author: hemantg
+author: HemantGaur
 ms.date: 05/27/2022
 ms.reviewer: jdaly
 ms.topic: article
@@ -38,7 +38,7 @@ When developing code components, you would follow the steps below:
 
 When your code component is ready for testing inside a model-driven app, canvas app, or portal, there are two ways to deploy a code component to Dataverse:
 
-1. [pac pcf push](/power-platform/developer/cli/reference/pcf#pac-pcf-push): This deploys a single code component at a time to a temporary **PowerAppsTools** solution.
+1. [pac pcf push](/power-platform/developer/cli/reference/pcf#pac-pcf-push): This deploys a single code component at a time to a solution specified by the `--solution-unique-name` parameter, or a temporary **PowerAppsTools** solution when no solution is specified.
 
 2. Using [pac solution init](/power-platform/developer/cli/reference/solution#pac-solution-init) and `msbuild` to build a `cdsproj` solution project that has references to one or more code components. Each code component is added to the `cdsproj` using [pac solution add-reference](/power-platform/developer/cli/reference/solution#pac-solution-add-reference). A solution project can contain references to multiple code components, whereas code component projects may only contain a single code component.
 

powerapps-docs/developer/component-framework/add-custom-controls-to-a-field-or-entity.md

@@ -1,8 +1,8 @@
 ---
 title: "Best practices for code components | Microsoft Docs"
 description: "Learn best practices and get guidance on how to use code components created using Power Apps component framework."
-ms.author: noazarur
-author: noazarur-microsoft
+ms.author: hemantg
+author: HemantGaur
 ms.date: 05/27/2022
 ms.reviewer: jdaly
 ms.topic: article

powerapps-docs/developer/component-framework/code-components-alm.md

@@ -1,8 +1,8 @@
 ---
 title: Code components for model-driven apps  | Microsoft Docs
 description: Learn how to create code components using Power Apps component framework for model-driven apps
-ms.author: noazarur
-author: noazarur-microsoft
+ms.author: hemantg
+author: HemantGaur
 ms.date: 05/27/2022
 ms.reviewer: jdaly
 ms.topic: article