Update

Author: Simonx Xu

support/dynamics/gp/combine-dynamicsdotdic-core-dictionary-and-extracted-dictionary-using-dexterity.md

@@ -81,6 +81,6 @@ If you combine an extracted source dictionary and a core dictionary, you create
 |source dictionary|A source dictionary is any Dexterity dictionary that is opened in Dexterity Utilities when you click **File** and then click **Open Source Dictionary**.|
 |third-party dictionary|Within the context of Dexterity, a third-party dictionary is an extracted dictionary that is from a product other than Microsoft Dynamics GP. Therefore, a third-party dictionary can be an extracted dictionary from another Microsoft product or from an independent software vendor.|
 
-For more information about how to create a chunk file from a Development Dictionary, see [How to create a chunk file in Great Plains 8.0 Dexterity](https://support.microsoft.com/help/894700).
+For more information about how to create a chunk file from a Development Dictionary, see [How to create a chunk file in Great Plains 8.0 Dexterity](create-a-chunk-file-dexterity.md).
 
 For more information about how to use Source Code Control to upgrade a Development Dictionary, see [How to upgrade a Dexterity-based application in Microsoft Dynamics GP or in Microsoft Great Plains by using the Dexterity Source Code Control Service](https://support.microsoft.com/help/910527).

support/dynamics/gp/create-a-chunk-file-dexterity.md

@@ -31,7 +31,7 @@ Before you create the chunk file, follow these steps in Dexterity:
 
 - Compile your development dictionary. To open the development dictionary, select **Open Source Dictionary** on the **File** menu. With your development dictionary open, select **Compile All** on the **Explorer** menu.
 - If you're using Dexterity Source Code Control, make sure that all resources are checked in. On the **Explorer** menu, select **Source Code**, and then select **Check In**.
-- Make sure that the **Resource IDs** that are assigned to the resources you created don't change values between builds. For more information, see [How to use an index file and the Microsoft Dynamics GP Dexterity source code control functionality to make sure that the resources that you create maintain the same resource ID in different builds and versions of your code](https://support.microsoft.com/help/894699).
+- Make sure that the **Resource IDs** that are assigned to the resources you created don't change values between builds. For more information, see [How to use an index file and the Microsoft Dynamics GP Dexterity source code control functionality to make sure that the resources that you create maintain the same resource ID in different builds and versions of your code](how-to-use-index-file-with-dexterity-to-maintain-resource-ids-in-new-builds-and-versions.md).
 
 > [!NOTE]
 > You can create a macro to record the following steps. You can then replay the macro later to re-create the chunk file or to modify the macro in a text editor to change the build number and any other details.

support/dynamics/gp/description-product-ids-dexterity.md

@@ -32,6 +32,6 @@ Microsoft Sales Operations assigns a unique product ID to every product. If two
 
 If you develop a custom product for a specific customer, you can obtain a single product ID. If you later decide to distribute the custom product to other customers, you can reuse this product ID for each customer. Although you use a single product ID, a different dictionary is used for each customer. When a different dictionary is used for each customer, the product ID remains unique at that customer site.
 
-If you want to include a functionality from one custom product in another custom product, copy the code to the dictionary for the new custom product. Or, create a separate dictionary for that functionality, and then obtain a new product ID for the functionality. For more information about how to create a chunk file, see [How to create a chunk file in Dexterity in Microsoft Dynamics GP](https://support.microsoft.com/help/894700)
+If you want to include a functionality from one custom product in another custom product, copy the code to the dictionary for the new custom product. Or, create a separate dictionary for that functionality, and then obtain a new product ID for the functionality. For more information about how to create a chunk file, see [How to create a chunk file in Dexterity in Microsoft Dynamics GP](create-a-chunk-file-dexterity.md)
 
 For more information, see [How to request a new Dexterity Product ID for my product](https://support.microsoft.com/help/867102)

support/dynamics/gp/gpconnection-object-replaces-retrieveglobals-dll.md

@@ -75,4 +75,4 @@ The Open method in the GPConnection object is **GPConnection.Open**. This method
 
 For more information about the RetrieveGlobals.dll and RetrieveGlobals9.dll files, click the following article number to view the article in the Microsoft Knowledge Base:
 
-[913341](https://support.microsoft.com/help/913341) How to use the new RetrieveGlobals9.dll file in Integration Manager and in Microsoft Dynamics GP 9.0
+[How to use the new RetrieveGlobals9.dll file in Integration Manager and in Microsoft Dynamics GP 9.0](upgrade-apps-to-use-gpconndll-gpconnnetdll-file.md)