Merge pull request #2835 from MicrosoftDocs/alm-cds-matp

Alm cds matp

Author: Mattp123

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](../../../maker/common-data-service/how-managed-solutions-merged.md).  
+see  [Merge option set options](/power-platform/alm/how-managed-solutions-merged).  
 
 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/use-multi-tenant-server-server-authentication.md

@@ -203,7 +203,7 @@ In this scenario any Common Data Service tenant can potentially use your multi-t
 
   For information about creating a Common Data Service solution, see the following topics:
 
-- [Use solutions for your customizations](../../maker/common-data-service/use-solutions-for-your-customizations.md)  
+- [Use solutions for your customizations](/power-platform/alm/use-solutions-for-your-customizations)  
 - [Package and distribute extensions using solutions](/dynamics365/customer-engagement/developer/package-distribute-extensions-use-solutions)  
 
   However, the application user cannot be included with a solution so you will need to provide a way to create this application user and associate it with the custom security role.  

powerapps-docs/developer/common-data-service/webapi/create-update-optionsets.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](../../../maker/common-data-service/how-managed-solutions-merged.md#merge-option-set-options).
+see [Merge option set options](/power-platform/alm/how-managed-solutions-merged#merge-option-set-options).
 
  ## Messages  
  The following table lists the messages that you can use with global option sets.  

powerapps-docs/maker/TOC.yml

@@ -1583,43 +1583,43 @@
   - name: Work with solutions
     href: ./common-data-service/solutions-overview.md
     items:
-    - name: Use solutions
-      href: ./common-data-service/use-solution-explorer.md
-    - name: Use a solution to customize
-      href: ./common-data-service/use-solutions-for-your-customizations.md
-    - name: Solution publisher overview
-      href: ./common-data-service/change-solution-publisher-prefix.md
-    - name: Use segmented solutions
-      href: ./common-data-service/use-segmented-solutions-patches-simplify-updates.md      
-    - name: How managed solutions are merged
-      href: ./common-data-service/how-managed-solutions-merged.md
-    - name: Use solution checker
-      href: ./common-data-service/use-powerapps-checker.md
-      items: 
-      - name: "Common issues and resolutions: solution checker"
-        href: ./common-data-service/common-issues-resolutions-solution-checker.md
-    - name: Best practices
-      href: ./common-data-service/solution-best-practices.md        
-    - name: "How to"
-      items:
-      - name: Create solution patches
-        href: ./common-data-service/solution-patches.md      
-      - name: Create a solution
-        href: ./common-data-service/create-solution.md
-      - name: Update or upgrade solutions
-        href: ./common-data-service/update-solutions.md
-      - name: Import solutions
-        href: ./common-data-service/import-update-export-solutions.md
-      - name: Export solutions
-        href: ./common-data-service/export-solutions.md               
-      - name: Use environment variables
-        href: ./common-data-service/EnvironmentVariables.md
-      - name: View solution layers
-        href: ./common-data-service/solution-layers.md
-      - name: View solution history
-        href: ./common-data-service/solution-history.md      
-      - name: Set managed properties in metadata
-        href: ./common-data-service/set-managed-properties-metadata.md      
+      - name: Use solutions
+        href: ./common-data-service/use-solution-explorer.md
+      - name: Solution publisher overview
+        href: ./common-data-service/change-solution-publisher-prefix.md
+      - name: Use segmented solutions
+        href: ./common-data-service/use-segmented-solutions-patches-simplify-updates.md      
+      - name: Use solution checker
+        href: ./common-data-service/use-powerapps-checker.md
+        items: 
+        - name: "Common issues and resolutions: solution checker"
+          href: ./common-data-service/common-issues-resolutions-solution-checker.md
+      - name: Best practices
+        href: ./common-data-service/solution-best-practices.md        
+      - name: "How to"
+        items:
+        - name: Create solution patches
+          href: ./common-data-service/solution-patches.md      
+        - name: Create a solution
+          href: ./common-data-service/create-solution.md
+        - name: Update or upgrade solutions
+          href: ./common-data-service/update-solutions.md
+        - name: Import solutions
+          href: ./common-data-service/import-update-export-solutions.md
+        - name: Export solutions
+          href: ./common-data-service/export-solutions.md               
+        - name: Use environment variables
+          href: ./common-data-service/EnvironmentVariables.md
+        - name: View solution layers
+          href: ./common-data-service/solution-layers.md
+        - name: View solution history
+          href: ./common-data-service/solution-history.md      
+        - name: Set managed properties in metadata
+          href: ./common-data-service/set-managed-properties-metadata.md
+        - name: "Advanced topics"
+          items:
+          - name: Create solution patches
+            href: ./common-data-service/solution-patches.md  
   - name: Work with dataflows
     href: ./common-data-service/self-service-data-prep-with-dataflows.md
     items:

powerapps-docs/maker/common-data-service/behavior-format-date-time-field.md

@@ -110,7 +110,7 @@ The following date and time related query operators are invalid for the **Date O
 [Create and edit fields](create-edit-fields.md)<br />
 [Define calculated fields to automate manual calculations](define-calculated-fields.md)<br />
 [Field managed properties](set-managed-properties-metadata.md#view-and-edit-field-managed-properties)<br />
-[Managed properties](solutions-overview.md#managed-properties)  
+[Managed properties](/power-platform/alm/managed-properties-alm)  
 [Blog: Working with time zones in the Common Data Service](https://powerapps.microsoft.com/en-us/blog/working-with-time-zones-in-the-common-data-service/)
 
 

powerapps-docs/maker/common-data-service/change-solution-publisher-prefix.md

@@ -26,22 +26,9 @@ search.app:
 
 Every app you create or customization you make is part of a solution. Every solution has a publisher. You specify the publisher when you create a solution. 
 
-> [!div class="mx-imgBorder"] 
-> <img src="media/solution-publisher-select.png" alt="Select solution publisher" height="731" width="416">
-
 The solution publisher indicates who developed the app. For this reason, you should create a solution publisher that is meaningful. You can view the solution publisher for a solution by selecting **Settings** from the **Solutions** area in Power Apps.
 
-## Solution publisher prefix
-A solution publisher includes a prefix. The prefix can help determine which publisher is responsible for the component. For example, the *Contoso solution* displayed here includes a solution publisher prefix that's *contoso*. 
-
-> [!div class="mx-imgBorder"] 
-> ![Fundraiser solution publisher prefix](media/publisher-prefix.png)
-
-> [!NOTE]
-> When you change a solution publisher prefix, you should do it before you create any new apps or metadata items. You can't change the names of metadata items. 
-
-## Common Data Services Default Solution
-The default solution in Power Apps is the Common Data Services Default Solution, which is associated with the Common Data Service Default Publisher. The default publisher prefix will be randomly assigned for this publisher, for example it could be *cr8a3*. This means that the name of every new item of metadata created in the default solution will have this prepended to the names used to uniquely identify the items. If you create a new entity named *Animal*, the unique name used by Common Data Service would be *cr8a3_animal*. The same is true for any new fields (attributes), relationships, or optionset options. If you will be customizing the default solution, consider changing the publisher prefix. 
+For more information about the solution publisher, see [Solution publisher](/power-platform/alm/solution-concepts-alm#solution-publisher).
 
 ## Create a solution publisher
 1.	In the Power Apps portal, select **Solutions**.