Merge pull request #7904 from MicrosoftDocs/jdaly-main-remove-pac-solution-clone

remove unneeded section

Author: JimDaly

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

@@ -3,7 +3,7 @@ title: Package a code component| Microsoft Docs
 description: This article describes how to import code components into model-driven apps in Microsoft Dataverse.
 ms.author: noazarur
 author: noazarur-microsoft
-ms.date: 08/16/2022
+ms.date: 03/22/2023
 ms.reviewer: jdaly
 ms.topic: article
 ms.subservice: pcf
@@ -103,25 +103,6 @@ To use the `push` capability, do the following:
    > [!NOTE]
    > The publisher prefix that you use with the `push` command should match the publisher prefix of your solution in which the components will be included.
 
-## Create a solution project based on an existing solution in Dataverse
-
-To create a solution project based on an existing solution in Dataverse, run the [pac solution clone](/power-platform/developer/cli/reference/solution) command.. To do so:
-
-1. Ensure that you have a valid authentication profile created.
-2. Run the command:
-
-   ```CLI
-   pac solution clone –-name(-n) <name of the solution to be exported> --targetversion(-v) <version of your solution> --include(-i) <settings that should be included>
-   ```
-
-   > [!NOTE]
-   > Settings Values: autonumbering, calendar, customization, emailtracking, externalapplications, general, isvconfig, marketing, outlooksynchronization, relationshiproles, sales.
-
-More information: [Settings options](/dotnet/api/microsoft.crm.sdk.messages.exportsolutionrequest)
-
-> [!NOTE]
-> Manually publish the customizations if you are importing unmanaged solution.
-
 ## Create a plug-in project and add a reference to it in your solution
 
 > [!NOTE]