Merge pull request #2453 from MicrosoftDocs/master

updating working

Author: mduelae

.openpublishing.redirection.json

@@ -1590,6 +1590,21 @@
       "source_path": "powerapps/maker/canvas-apps/release-notes.md",
       "redirect_url": "/powerapps/whats-new",
       "redirect_document_id": true
+    },
+    {
+      "source_path": "powerapps-docs/developer/common-data-service/understand-managed-solutions-merged.md",
+      "redirect_url": "../../maker/common-data-service/how-managed-solutions-merged",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "powerapps-docs/maker/common-data-service/navigate-specific-solution.md",
+      "redirect_url": "use-solution-explorer",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "powerapps-docs/maker/common-data-service/publish-changes-for-use-customer-service-hub.md",
+      "redirect_url": "create-solution#publish-changes",
+      "redirect_document_id": true
     }
   ]
 }

powerapps-docs/developer/common-data-service/org-service/extend-code-generation-tool.md

@@ -127,5 +127,4 @@ Guid accountId = service.Create(account);
 
  [Create Early-Bound Entity Classes with the Code Generation Tool (CrmSvcUtil.exe)](/dynamics365/customer-engagement/developer/create-early-bound-entity-classes-code-generation-tool)<br />
  [Use the Early Bound Entity Classes for Create, Update and Delete](/dynamics365/customer-engagement/developer/use-entity-class-create-update-delete)<br />
- [Troubleshooting Tips](/dynamics365/customer-engagement/developer/troubleshooting-tips)<br />
  [Run a simple program using Web services](/dynamics365/customer-engagement/developer/simple-program-web-services)

powerapps-docs/developer/common-data-service/org-service/metadata-option-sets.md

@@ -25,7 +25,7 @@ new `OptionMetadata` instance. When you define an option, it will contain an opt
 context of the publisher set for the solution that the option set is created in. 
 This prefix helps reduce the chance of creating duplicate option sets for a managed solution, 
 and in any option sets that are defined in organizations where your managed solution is installed. For more information, 
-see [Merge option set options](../understand-managed-solutions-merged.md#merge-option-set-options).  
+see [Merge option set options](../../../maker/common-data-service/how-managed-solutions-merged.md).  
 
 You can download the sample from [here](https://github.com/microsoft/PowerApps-Samples/tree/master/cds/orgsvc/C%23/WorkWithOptionSets).
 

powerapps-docs/developer/common-data-service/understand-managed-solutions-merged.md

@@ -31,7 +31,7 @@ new `OptionMetadata` instance. When you define an option, it will contain an opt
 context of the publisher set for the solution that the option set is created in. 
 This prefix helps reduce the chance of creating duplicate option sets for a managed solution, 
 and in any option sets that are defined in organizations where your managed solution is installed. For more information, 
-see [Merge option set options](../understand-managed-solutions-merged.md#merge-option-set-options).
+see [Merge option set options](../../../maker/common-data-service/how-managed-solutions-merged.md#merge-option-set-options).
 
  ## Messages  
  The following table lists the messages that you can use with global option sets.