Adding links to dev topic per Shan email Mechanisms to migrate data due to schema change

Author: Mattp123

powerapps-docs/maker/common-data-service/create-solution.md

@@ -198,4 +198,4 @@ Start by opening an unmanaged solution you created. Choose the **Entity** compon
 
 ### See also
  [Use solutions](use-solution-explorer.md) 
-[For Developers: Create, export, or import an unmanaged solution](/power-platform/alm/solution-api#create-export-or-import-an-unmanaged-solution)
+[For developers: Create, export, or import an unmanaged solution](/power-platform/alm/solution-api#create-export-or-import-an-unmanaged-solution)

powerapps-docs/maker/common-data-service/export-solutions.md

@@ -128,3 +128,4 @@ More information:   [Service Calendar Appearance Configuration](https://docs.mic
 ### See also
 [Import solutions](import-update-export-solutions.md) <br />
 [Update solutions](update-solutions.md)
+[For developers: Create, export, or import an unmanaged solution](/power-platform/alm/solution-api#create-export-or-import-an-unmanaged-solution)

powerapps-docs/maker/common-data-service/import-update-export-solutions.md

@@ -62,4 +62,4 @@ To import a solution:
 [Update solutions](update-solutions.md) <br />
 [Export solutions](export-solutions.md) <br />
 [Publish changes](create-solution.md#publish-changes)
-
+[For developers: Create, export, or import an unmanaged solution](/power-platform/alm/solution-api#create-export-or-import-an-unmanaged-solution)

powerapps-docs/maker/common-data-service/update-solutions.md

@@ -88,3 +88,4 @@ A solution’s version has the following format: major.minor.build.revision. An
 [Export solutions](export-solutions.md) <br />
 [Import solutions](import-update-export-solutions.md) <br />
 [Create solution patches](/powerapps/maker/common-data-service/solution-patches)
+[For developers: Cloning, patching, and upgrading](/power-platform/alm/solution-api#cloning-patching-and-upgrading)

powerapps-docs/maker/common-data-service/view-component-dependencies.md

@@ -25,4 +25,7 @@ Solution components often depend on other solution components. You can’t delet
 2. Open the solution you want, select the component you want, on the command bar select **...,** and then select **Show dependencies**. 
 
    > [!div class="mx-imgBorder"] 
-   > ![Component dependency for the account entity](media/component-dependencies-account.png)
+   > ![Component dependency for the account entity](media/component-dependencies-account.png)
+
+### See also
+[For developers: Detect solution dependencies](/power-platform/alm/solution-api#detect-solution-dependencies)