Merge pull request #3006 from MicrosoftDocs/pehecke-solutions-update

Solution content migration to Power Platform

Author: phecke

.openpublishing.publish.config.json

@@ -38,10 +38,6 @@
           "ConceptualTOC": "powerapps-docs/developer/common-data-service/org-service/toc.yml",
           "ReferenceTOCUrl": "/dotnet/api/ce-9-general/toc.json"
         },
-        {
-          "ConceptualTOC": "powerapps-docs/developer/common-data-service/package-deployer/toc.yml",
-          "ReferenceTOCUrl": "/dotnet/api/ce-9-packagedeployer/toc.json"
-        },
         {
           "ConceptualTOC": "powerapps-docs/developer/common-data-service/workflow/toc.yml",
           "ReferenceTOCUrl": "/dotnet/api/ce-9-workflow/toc.json"

.openpublishing.redirection.json

@@ -30,11 +30,16 @@
       "redirect_url": "https://docs.microsoft.com/power-platform/alm/checker-api/upload-file",
       "redirect_document_id": "false"
     }, 
+    {
+      "source_path": "powerapps-docs/developer/common-data-service/package-deployer/create-packages-package-deployer.md",
+      "redirect_url": "https://docs.microsoft.com/power-platform/alm/package-deployer-tool",
+      "redirect_document_id": "false"
+    }, 
     {
       "source_path": "powerapps-docs/maker/common-data-service/create-edit-entities.md",
       "redirect_url": "data-platform-create-entity",
       "redirect_document_id": "false"
-    }, 
+    },
     {
       "source_path": "powerapps-docs/maker/common-data-service/solution-patches.md",
       "redirect_url": "https://docs.microsoft.com/power-platform/alm/update-solutions-alm#create-solution-patches",

powerapps-docs/developer/common-data-service/TOC.yml

@@ -340,8 +340,6 @@
     items:
     - name: Source control with solution files
       href: use-source-control-solution-files.md       
-  - name: Package Deployer tool
-    href: package-deployer/create-packages-package-deployer.md
   - name: Publish your app on AppSource
     href: publish-app-appsource.md
     items:

powerapps-docs/developer/common-data-service/appendix-app-certification-checklist.md

@@ -57,7 +57,7 @@ The following checklist provides the list of validations performed by Microsoft
 <td>Deployment Validation</td>
 <td>
 <ul>
-<li>Solution will be installed to a Power Apps studio using <a href="https://docs.microsoft.com/powerapps/developer/common-data-service/package-deployer/create-packages-package-deployer">Package Deployer</a>. Installed canvas apps will be manually located in the solution as well as on Apps section after installation and will make sure the app is opened in edit and run mode. Canvas App will be manually deleted from Power Apps studio to validate successful uninstallation</li>
+<li>Solution will be installed to a Power Apps studio using <a href="https://docs.microsoft.com/power-platform/alm/package-deployer-tool">Package Deployer</a>. Installed canvas apps will be manually located in the solution as well as on Apps section after installation and will make sure the app is opened in edit and run mode. Canvas App will be manually deleted from Power Apps studio to validate successful uninstallation</li>
 <li>Check the canvas app successfully connects through the connectors provided by the publishers. For example, Common Data Service or any other connections.</li>
 <li>Check all Common Data Service components (entities, web resources, plug-ins and other components) are available in the solution.</li>
 <li>Manually uninstall the solution and check if all the components associated to the managed solution is removed.</li>

powerapps-docs/developer/common-data-service/create-package-app-appsource.md

@@ -32,7 +32,7 @@ You must create an AppSource package (.zip file) to include your solution and de
 
 A package lets you bundle and deploy multiple files related to your app at once. 
 
-1. Create a Dynamics 365 package to include the solution and configuration data files that you created in [Step 2: Create a managed solution for your app](create-solution-app-appsource.md). A package can also contain custom code that can run before, while, or after the package is deployed to the Common Data Service instance. For more information about creating a package file, see [Create packages for the Dynamics 365 Package Deployer](/dynamics365/customer-engagement/developer/create-packages-package-deployer).
+1. Create a Dynamics 365 package to include the solution and configuration data files that you created in [Step 2: Create a managed solution for your app](create-solution-app-appsource.md). A package can also contain custom code that can run before, while, or after the package is deployed to the Common Data Service instance. For more information about creating a package file, see [Create packages for the Package Deployer](/power-platform/alm/package-deployer-tool).
 
     After you have created a package, your package will consist of the following things:
 

powerapps-docs/developer/common-data-service/developer-tools.md

@@ -28,7 +28,7 @@ The following tools are distributed in NuGet packages. The [Developer Guide: Dow
 |---------|---------|
 |Code generation tool `CrmSvcUtil.exe`|A command-line code generation tool that generates early-bound .NET Framework classes that represent the entity data model used by the organization service. <br />More information: <br />[Organization Service](work-with-data-cds.md#organization-service)<br />[Create early bound entity classes with the code generation tool](/dynamics365/customer-engagement/developer/org-service/create-early-bound-entity-classes-code-generation-tool)|
 |Configuration Migration tool `DataMigrationUtility.exe`|Used to move configuration data across environments. Configuration data is used to define custom functionality  and is typically stored in custom entities. This tool is not designed to move business data. <br /> More information: [Common Data Service Administrator Guide: Move configuration data across instances and organizations with the Configuration Migration tool](/dynamics365/customer-engagement/admin/manage-configuration-data)|
-|Package Deployer `PackageDeployer.exe`|Used to deploy packages on Common Data Service instances. A package is an installable unit that includes solutions. <br /> More information: <br />[Deploy Solution Packages](introduction-solutions.md#deploy-solution-packages)<br />[Create packages for the Common Data Service Package Deployer](/dynamics365/customer-engagement/developer/create-packages-package-deployer)|
+|Package Deployer `PackageDeployer.exe`|Used to deploy packages on Common Data Service instances. A package is an installable unit that includes solutions. <br /> More information: <br />[Deploy Solution Packages](introduction-solutions.md#deploy-solution-packages)<br />[Create packages for the Package Deployer](/power-platform/alm/package-deployer-tool)|
 |Plug-in Registration Tool `PluginRegistration.exe`|A tool used to subscribe .NET assembly plug-in classes to server events. <br />More information: <br />[Create a plug-in](apply-business-logic-with-code.md#create-a-plug-in)<br />[Register a plug-in](register-plug-in.md)|
 |SolutionPackager tool `SolutionPackager.exe`|A tool that can reversibly decompose a Common Data Service compressed solution file into multiple XML files and other files so that these files can be easily managed by a source control system.<br /> More information: <br />[Team development of solutions](introduction-solutions.md#team-development-of-solutions)<br />[Use the SolutionPackager tool to compress and extract a solution file](/dynamics365/customer-engagement/developer/compress-extract-solution-file-solutionpackager)|
 
@@ -81,7 +81,7 @@ More information [Build Windows client applications using the XRM tools](/dynami
 
 Use these assemblies to create packages for the Package Deployer.
 
-More information: [Create packages for the Common Data Service Package Deployer](/dynamics365/customer-engagement/developer/create-packages-package-deployer)
+More information: [Create packages for the Package Deployer](/power-platform/alm/package-deployer-tool)
 
 **NuGet Package**: [Microsoft.CrmSdk.XrmTooling.PackageDeployment](https://www.nuget.org/packages/Microsoft.CrmSdk.XrmTooling.PackageDeployment/)
 

powerapps-docs/developer/common-data-service/get-started-CDS-developers.md

@@ -58,7 +58,7 @@ If you are going to distribute the extensions you create or any customizations t
 
  - [Introduction to solutions](introduction-solutions.md)
  - [SolutionPackager tool](compress-extract-solution-file-solutionpackager.md)
- - [Package Deployer tool](./package-deployer/create-packages-package-deployer.md)
+ - [Package Deployer tool](/power-platform/alm/package-deployer-tool)
  - [Publish your app on AppSource](publish-app-appsource.md)
 
 ## Create client applications and authentication

powerapps-docs/developer/common-data-service/introduction-solutions.md

@@ -147,7 +147,7 @@ Use the *Package Deployer* to create a custom installer for a package that can i
 - Custom code that can run before, while, or after the package is deployed.
 - HTML content specific to the package that can display at the beginning and end of the deployment process. This can be useful to provide a description of the solutions and files that are deployed in the package.
 
-More information: [Create packages for the Common Data Service Package Deployer](package-deployer/create-packages-package-deployer.md).
+More information: [Create packages for the Package Deployer](/power-platform/alm/package-deployer-tool).
 
 ## Team development of solutions
 

powerapps-docs/developer/common-data-service/isv-app-management-appsource-checker.md

@@ -27,7 +27,7 @@ search.app:
 
 You can use the AppSource checker to verify whether your app has met certification criteria before you submit it to [AppSource](https://appsource.microsoft.com/). The checker lets you know whether your solution file has errors that need to be corrected and verifies whether AppSource certification criteria have been met. 
 
-In ISV Studio, you can upload either a full [package](/powerapps/developer/common-data-service/package-deployer/create-packages-package-deployer) or solution(s). You'll be notified whether any issues need to be remediated.
+In ISV Studio, you can upload either a full [package](/power-platform/alm/package-deployer-tool) or solution(s). You'll be notified whether any issues need to be remediated.
 
 **To run AppSource checker**