Fixed references and other issues

Author: Bishal Goswami

.openpublishing.publish.config.json

@@ -31,27 +31,27 @@
       },
       "JoinTOCPlugin": [
         {
-          "ConceptualTOC": "powerapps-docs/developer/common-data-service/webapi/toc.yml",
+          "ConceptualTOC": "powerapps-docs/developer/data-platform/webapi/toc.yml",
           "ReferenceTOCUrl": "/dynamics365/customer-engagement/web-api/toc.json"
         },
         {
-          "ConceptualTOC": "powerapps-docs/developer/common-data-service/org-service/toc.yml",
+          "ConceptualTOC": "powerapps-docs/developer/data-platform/org-service/toc.yml",
           "ReferenceTOCUrl": "/dotnet/api/ce-9-general/toc.json"
         },
         {
-          "ConceptualTOC": "powerapps-docs/developer/common-data-service/workflow/toc.yml",
+          "ConceptualTOC": "powerapps-docs/developer/data-platform/workflow/toc.yml",
           "ReferenceTOCUrl": "/dotnet/api/ce-9-workflow/toc.json"
         },
         {
-          "ConceptualTOC": "powerapps-docs/developer/common-data-service/xrm-tooling/toc.yml",
+          "ConceptualTOC": "powerapps-docs/developer/data-platform/xrm-tooling/toc.yml",
           "ReferenceTOCUrl": "/dotnet/api/ce-9-xrmtooling/toc.json"
         },
         {
-          "ConceptualTOC": "powerapps-docs/developer/common-data-service/virtual-entities/toc.yml",
+          "ConceptualTOC": "powerapps-docs/developer/data-platform/virtual-entities/toc.yml",
           "ReferenceTOCUrl": "/dotnet/api/ce-9-virtualentity/toc.json"
         },
         {
-          "ConceptualTOC": "powerapps-docs/developer/common-data-service/online-management-api/toc.yml",
+          "ConceptualTOC": "powerapps-docs/developer/data-platform/online-management-api/toc.yml",
           "ReferenceTOCUrl": "/rest/api/dynamics365/toc.json"
         }
       ]

.openpublishing.redirection.json

@@ -12,7 +12,7 @@
       items:
       # Adding Create app for each type of app
       - name: Create apps
-        tocHref: /powerapps/maker/common-data-service/
+        tocHref: /powerapps/maker/data-platform/
         topicHref: /powerapps/maker/index
       - name: Create apps
         tocHref: /powerapps/maker/model-driven-apps/
@@ -22,23 +22,23 @@
         topicHref: /powerapps/maker/index       
       #  Make sure Create apps appears for topics in developer folder 
       - name: Create apps
-        tocHref: /powerapps/developer/common-data-service/
+        tocHref: /powerapps/developer/data-platform/
         topicHref: /powerapps/maker/index
         items: 
         - name: Microsoft Dataverse
-          tocHref: /powerapps/developer/common-data-service/
-          topicHref: /powerapps/maker/common-data-service/index          
+          tocHref: /powerapps/developer/data-platform/
+          topicHref: /powerapps/maker/data-platform/index          
           items:
           - name: Developer
-            tocHref: /powerapps/developer/common-data-service/
-            topicHref: /powerapps/developer/common-data-service/index
+            tocHref: /powerapps/developer/data-platform/
+            topicHref: /powerapps/developer/data-platform/index
             items:
             - name: Organization Service
-              tocHref: /powerapps/developer/common-data-service/org-service/
-              topicHref: /powerapps/developer/common-data-service/org-service/index
+              tocHref: /powerapps/developer/data-platform/org-service/
+              topicHref: /powerapps/developer/data-platform/org-service/index
             - name: Web API
-              tocHref: /powerapps/developer/common-data-service/webapi/
-              topicHref: /powerapps/developer/common-data-service/webapi/index
+              tocHref: /powerapps/developer/data-platform/webapi/
+              topicHref: /powerapps/developer/data-platform/webapi/index
       - name: Create apps
         tocHref: /powerapps/developer/model-driven-apps/
         topicHref: /powerapps/maker/index

powerapps-docs/breadcrumb/toc.yml

@@ -65,7 +65,7 @@ To add code components to a canvas app:
 2. Create a new canvas app or edit an existing app to which you want to add the code component.
 
    > [!IMPORTANT]
-   > Make sure the solution zip file is already [imported](https://docs.microsoft.com/powerapps/maker/common-data-service/import-update-export-solutions) into Microsoft Dataverse before you proceed to the next step.
+   > Make sure the solution zip file is already [imported](https://docs.microsoft.com/powerapps/maker/data-platform/import-update-export-solutions) into Microsoft Dataverse before you proceed to the next step.
 
 3. Go to **Insert** > **Custom** > **Import component**. 
 

powerapps-docs/developer/component-framework/component-framework-for-canvas-apps.md

@@ -15,7 +15,7 @@ ms.assetid: f393f227-7a88-4f25-9036-780b3bf14070
 
 # Get tooling for Power Apps component framework
 
-Use **Microsoft Power Apps CLI** (command-line interface) to create, debug, and deploy code components using Power Apps component framework. Power Apps CLI enables developers to create code components quickly. In the future, it will be expanded to include support for additional development and application life cycle management (ALM) experiences. More information: [Install Power Apps CLI](../common-data-service/powerapps-cli.md)
+Use **Microsoft Power Apps CLI** (command-line interface) to create, debug, and deploy code components using Power Apps component framework. Power Apps CLI enables developers to create code components quickly. In the future, it will be expanded to include support for additional development and application life cycle management (ALM) experiences. More information: [Install Power Apps CLI](../data-platform/powerapps-cli.md)
 
 > [!IMPORTANT]
 > To deploy your code component using Power Apps CLI, you must have a Microsoft Dataverse environment with system administrator or system customizer privileges.

powerapps-docs/developer/component-framework/get-powerapps-cli.md

@@ -344,7 +344,7 @@ npm start
 
 ## Packaging your code components
 
-Follow these steps to create and import a [solution](https://docs.microsoft.com/powerapps/maker/common-data-service/solutions-overview) file:
+Follow these steps to create and import a [solution](https://docs.microsoft.com/powerapps/maker/data-platform/solutions-overview) file:
 
 1. Create a new folder **Solutions** inside the **LinearComponent** folder and navigate into the folder. 
 2. Create a new solution project in the **LinearComponent** folder using the following command:
@@ -354,7 +354,7 @@ Follow these steps to create and import a [solution](https://docs.microsoft.com/
     ```
 
    > [!NOTE]
-   > The [publisher-name](https://docs.microsoft.com/powerapps/developer/common-data-service/reference/entities/publisher) and [publisher-prefix](https://docs.microsoft.com/powerapps/maker/common-data-service/change-solution-publisher-prefix) values must be unique to your environment.
+   > The [publisher-name](https://docs.microsoft.com/powerapps/developer/data-platform/reference/entities/publisher) and [publisher-prefix](https://docs.microsoft.com/powerapps/maker/data-platform/change-solution-publisher-prefix) values must be unique to your environment.
 
 3. Once the new solution project is created, you need to refer to the ___location where the created component is located. You can add the reference by using the following command:
 
@@ -384,7 +384,7 @@ Follow these steps to create and import a [solution](https://docs.microsoft.com/
     > - Under **Code Tools**, check **NuGet targets & Build Tasks**.
 
 6. The generated solution zip file is located in the `Solution\bin\debug` folder.
-7. Manually [import the solution into Dataverse](https://docs.microsoft.com/powerapps/maker/common-data-service/import-update-export-solutions) using the web portal once the zip file is ready or automatically using the [Microsoft Power Platform Build Tools](https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerPlatform-BuildTools).
+7. Manually [import the solution into Dataverse](https://docs.microsoft.com/powerapps/maker/data-platform/import-update-export-solutions) using the web portal once the zip file is ready or automatically using the [Microsoft Power Platform Build Tools](https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerPlatform-BuildTools).
 
 ## Adding code components in model-driven apps
 
@@ -399,6 +399,6 @@ To add the code components to a canvas app, follow the steps in the article [Add
 [Download sample components](https://github.com/microsoft/PowerApps-Samples/tree/master/component-framework)<br/>
 [Learn Power Apps component framework](https://docs.microsoft.com/learn/paths/use-power-apps-component-framework)<br/>
 [Update existing Power Apps component framework components](updating-existing-controls.md)<br/>
-[Microsoft Power Platform Build Tools](https://docs.microsoft.com/powerapps/developer/common-data-service/build-tools-overview)<br/>
+[Microsoft Power Platform Build Tools](https://docs.microsoft.com/powerapps/developer/data-platform/build-tools-overview)<br/>
 [Power Apps component framework API reference](reference/index.md)<br/>
 [Power Apps component framework overview](overview.md)

powerapps-docs/developer/component-framework/implementing-controls-using-typescript.md

@@ -47,7 +47,7 @@ To create and import a solution file:
     > - If you encounter an error that says *Ambiguous project name* when running the `msbuild` command on your solution, ensure that your solution name and project name are not the same.
 
 4. The generated solution files are located inside the `\bin\debug\` folder after the build is successful.
-5. Manually [import the solution into Dataverse](https://docs.microsoft.com/powerapps/maker/common-data-service/import-update-export-solutions) using the web portal or automatically using the [Microsoft Power Platform Build Tools](https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerPlatform-BuildTools).
+5. Manually [import the solution into Dataverse](https://docs.microsoft.com/powerapps/maker/data-platform/import-update-export-solutions) using the web portal or automatically using the [Microsoft Power Platform Build Tools](https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerPlatform-BuildTools).
 
 ## Connecting to your environment
 

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

@@ -18,5 +18,5 @@ ms.author: nabuthuk
 
 After you have tested your code components and want it to distribute to others to use it, you must publish it on Microsoft AppSource.
 
-For detailed information on how to publish your code components on AppSource, see [Publish your app on AppSource](/powerapps/developer/common-data-service/publish-app-appsource).
+For detailed information on how to publish your code components on AppSource, see [Publish your app on AppSource](/powerapps/developer/data-platform/publish-app-appsource).
 

powerapps-docs/developer/component-framework/publish-components-app-source.md

@@ -54,5 +54,5 @@ Follow the steps below to import and try the sample components in your model-dri
      msbuild /t:restore
     ```
 1. Again, run the command `msbuild`.
-1. The generated solution zip file will be available at `Solution\bin\debug` folder. Manually [import the solution](/powerapps/maker/common-data-service/import-update-export-solutions) into your Microsoft Dataverse environment using the web portal once the zip file is ready. Alternatively, to import the solution using Power Apps CLI commands, see the [Connecting to your environment](https://docs.microsoft.com/powerapps/developer/component-framework/import-custom-controls#connecting-to-your-environment) and [Deployment](https://docs.microsoft.com/powerapps/developer/component-framework/import-custom-controls#deploying-code-components) sections.
+1. The generated solution zip file will be available at `Solution\bin\debug` folder. Manually [import the solution](/powerapps/maker/data-platform/import-update-export-solutions) into your Microsoft Dataverse environment using the web portal once the zip file is ready. Alternatively, to import the solution using Power Apps CLI commands, see the [Connecting to your environment](https://docs.microsoft.com/powerapps/developer/component-framework/import-custom-controls#connecting-to-your-environment) and [Deployment](https://docs.microsoft.com/powerapps/developer/component-framework/import-custom-controls#deploying-code-components) sections.
 1. Finally, to add code components to your model-driven and canvas apps, see [Add components to model-driven apps](https://docs.microsoft.com/powerapps/developer/component-framework/add-custom-controls-to-a-field-or-entity) and [Add components to canvas apps](https://docs.microsoft.com/powerapps/developer/component-framework/component-framework-for-canvas-apps#add-components-to-a-canvas-app).

powerapps-docs/developer/component-framework/use-sample-components.md

@@ -3,7 +3,7 @@
 - name: Overview
   href: overview.md
 - name: Get started
-  href: get-started-cds-developers.md
+  href: get-started-developers.md
   items:
   - name: Supported customizations
     href: supported-customizations.md
@@ -19,7 +19,7 @@
   - name: Verifying access in code
     href: security-access-coding.md
 - name: Work with data using code
-  href: work-with-data-cds.md
+  href: work-with-data.md
   items:
   - name: Use Web API
     href: webapi/index.md
@@ -59,9 +59,9 @@
     - name: Improve FetchXML request performance
       href: fetchxml-performance.md
   - name: "Use SQL to query data"
-    href: cds-sql-query.md
+    href: dataverse-sql-query.md
   - name: "Dataverse SQL"
-    href: how-cds-sql-differs-from-transact-sql.md
+    href: how-dataverse-sql-differs-from-transact-sql.md
   - name: Saved Queries
     href: saved-queries.md
   - name: Query Hierarchical data
@@ -171,7 +171,7 @@
   - name: Data Export Service
     href: data-export-service.md
   - name: Migrate data between environments using OData dataflows
-    href: cds-odata-dataflows-migration.md
+    href: dataverse-odata-dataflows-migration.md
   - name: Synchronize data
     href: data-synchronization.md
     items:
@@ -370,7 +370,7 @@
     - name: Install failures analytics
       href: isv-install-failure-analytics.md
 - name: Create client applications
-  href: connect-cds.md
+  href: connect-dataverse.md
   items:
   - name: Authenticate
     href: authentication.md