Merge branch 'main' into ado-14130

Author: nickdoelman

.openpublishing.redirection.json

@@ -7250,16 +7250,6 @@
       "redirect_url": "powerapps-docs/maker/portals/admin/update-dynamics365-instance.md",
       "redirect_document_id": "false"
     },
-    {
-      "source_path": "powerapps-docs/user/cs-email-template-builder.md",
-      "redirect_url": "/dynamics365/customer-service/cs-email-template-builder",
-      "redirect_document_id": false
-    },
-    {
-      "source_path": "powerapps-docs/user/customize-insert-email-template.md",
-      "redirect_url": "/dynamics365/customer-service/customize-insert-email-template",
-      "redirect_document_id": "false"
-    },
     {
       "source_path": "powerapps-docs/teams/boards-architecture.md",
       "redirect_url": "https://github.com/microsoft/teams-powerapps-app-templates",

powerapps-docs/developer/data-platform/tools/devtools-create-plugin.md

@@ -2,7 +2,7 @@
 title: "Quickstart: Create a plug-in using Power Platform Tools | Microsoft Docs"
 description: "Learn how to create and register a Dataverse plug-in using the Power Platform Tools extension for Visual Studio."
 ms.custom: ""
-ms.date: 06/20/2020
+ms.date: 01/27/2023
 ms.reviewer: "pehecke"
 
 ms.topic: "article"
@@ -25,10 +25,9 @@ If you already have an existing Dataverse solution set up, then follow these [in
 
 ## Prerequisites
 
-- Visual Studio 2019
+- Visual Studio 2019 or 2022
 - Power Platform Tools extension for Visual Studio
-- C# language
-- .NET Framework 4.6.2 (only for plug-in or custom workflow activity development)
+- .NET Framework 4.6.2 is required for plug-in or custom workflow activity development
 - Power Apps/Dataverse subscription or a trial environment
 
 ## Connect to your Dataverse environment

powerapps-docs/developer/data-platform/tools/devtools-create-project.md

@@ -2,7 +2,7 @@
 title: "Quickstart: Create a Power Platform Tools project | Microsoft Docs"
 description: "Learn how to start a new Visual Studio project for plug-in or custom workflow assembly development using Power Platform Tools."
 ms.custom: ""
-ms.date: 06/20/2020
+ms.date: 01/27/2023
 ms.reviewer: "pehecke"
 
 ms.topic: "article"
@@ -23,10 +23,10 @@ Like any Visual Studio solution, you begin by creating a new project. In the new
 
 ## Prerequisites
 
-- Visual Studio 2019
+- Visual Studio 2019 or 2022
 - Power Platform Tools for Visual Studio
 - C# language
-- .NET Framework 4.6.2 (only for plug-in or custom workflow activity development)
+- .NET Framework 4.6.2 or greater - (plug-in and custom workflow activity development requires v4.6.2)
 - Power Apps/Dataverse subscription or a trial environment
 - Windows Workflow Foundation (only for custom workflow activity development)
 
@@ -61,7 +61,7 @@ The easy way to create a Power Platform solution containing a CrmPackage project
 
 1. In the Visual Studio new project dialog, search for and choose **Power Platform Solution Template** and then select **Next**.
 
-1. Enter the requested project information, choose .NET Framework 4.6.2 or 4.7.2, and select **Create**. <p/>At this point you should see either a Dataverse login dialog or a dialog to reuse your last Dataverse connection. Do whatever is appropriate to connect to your Dataverse development environment. Never develop code in a production environment.
+1. Enter the requested project information, choose a .NET Framework version, and select **Create**. <p/>At this point you should see either a Dataverse login dialog or a dialog to reuse your last Dataverse connection. Do whatever is appropriate to connect to your Dataverse development environment. Never develop code in a production environment.
 
 1. At the **Configure Microsoft Power Platform Solution** dialog, choose either to use an existing Dataverse solution or create a new solution. <p/>Depending on what you have chosen, you will either be prompted to enter information about the new solution or select the existing solution from a drop-down list. **Step #3 Select Solution** is displayed but won't be active until you are logged in and choose **Next** in step #2.
 
@@ -85,7 +85,7 @@ Only projects created with a Power Platform Tools template should be added to a
 
 1. Select one of the installed Power Platform Tools templates and select **Next**.
 
-1. Fill in any required information and select **Create**. For a plug-in or workflow activity library, be sure to choose .NET Framework 4.6.2 (or 4.7.2).
+1. Fill in any required information and select **Create**. For a plug-in or workflow activity library, be sure to choose .NET Framework 4.6.2.
 
 ### Add an existing project to a Power Platform solution
 

powerapps-docs/developer/data-platform/tools/devtools-install.md

@@ -2,7 +2,7 @@
 title: "Install Power Platform Tools | Microsoft Docs"
 description: "Learn how to install the Power Platform Tools extension for Visual Studio."
 ms.custom: ""
-ms.date: 06/20/2022
+ms.date: 01/27/2023
 ms.reviewer: "pehecke"
 
 ms.topic: "article"
@@ -30,7 +30,7 @@ Power Platform Tools for Visual Studio supports the rapid creation, debugging, a
 
 Before installing Power Platform Tools into Visual Studio you must have the following applications and frameworks installed on your development computer:
 
-- Microsoft Visual Studio 2019.
+- Microsoft Visual Studio 2019 or 2022.
 
 - .NET Framework 4.6.2 (required only for plug-in and workflow activity development)
 
@@ -82,6 +82,7 @@ You can find a few Power Platform Tools options in Visual Studio by choosing **T
 ### See Also
 
 [Quickstart: Create a Power Platform Tools project](devtools-create-project.md)  
-[Power Platform Tools on the Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerPlatformTools)
+[Power Platform Tools extension for Visual Studio 2019](https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerPlatformTools)  
+[Power Platform Tools extension for Visual Studio 2022](https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerPlatformToolsVS2022)
 
 [!INCLUDE[footer-include](../../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/virtual-entities/get-started-ve.md

@@ -64,7 +64,7 @@ Following are the limitations in virtual tables that must be considered.
     - A column on a virtual table cannot be calculated or rollup.  Any desired calculations must be done on the external side, possibly within or directed by the data provider.
     - Although you can add virtual table columns as a lookup on a grid or other UI views, you cannot filter or sort based on this virtual table lookup column.
 - Auditing is not supported.
-- Search functionality is not support for virtual tables as they do not persist data.
+- Search functionality is not supported for virtual tables as they do not persist data.
 - Charts and dashboards are not supported for virtual tables.
 - Virtual tables cannot be enabled for queues.
 - Offline caching of values is not supported for virtual tables.