Merge branch 'master' into portals-iframe-VA

Author: tapanm-MSFT

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

@@ -37,7 +37,7 @@ Because the default solution contains all the solutions components, it may be ea
     |-----------|-----------------|  
     |**Display Name**|The name shown in the list of solutions. You can change this later.|  
     |**Name**|The unique name of the solution. This is generated using the value you enter in the Display Name field. You can edit this before you save the solution, but after you save the solution, you can’t change it.|  
-    |**Publisher**|You can select the default publisher or create a new publisher. Unless you plan to distribute your solution, you should just use the default publisher for your organization.|  
+    |**Publisher**|You can select the default publisher or create a new publisher. We recommend that you create a publisher for your organization to use consistently across your environments that you will use the solution in. More information: [Change the solution publisher prefix for any publisher](change-solution-publisher-prefix.md#change-the-solution-publisher-prefix-for-any-publisher) |  
     |**Version**|Enter a number for the version of your solution. This is only important if you export your solution. The version number will be included in the file name when you export the solution.|  
 
 3.  Select **Save**.  

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

@@ -35,7 +35,7 @@ More information: [Whitepaper: Solution Lifecycle Management](https://www.micros
   
 
 <a name="BKMK_SolutionComponents"></a>   
-### Components  
+## Components  
  A component represents something that you can potentially customize. Anything that can be included in a solution is a component. To view the components included in a solution, in solution explorer go to **Settings** > **Solutions** and then open the solution you want. The components are listed in the **Components** list. 
 
 > [!div class="mx-imgBorder"] 
@@ -116,7 +116,7 @@ To view a list of component types that can be added to any solution, see [Compon
  The purpose of having components is to keep track of any limitations on what can be customized using managed properties and all the dependencies so that it can be exported, imported, and (in managed solutions) deleted without leaving anything behind.  
 
 <a name="BKMK_ManagedAndUnmanagedSolutions"></a>   
-### Managed and unmanaged solutions  
+## Managed and unmanaged solutions  
  There are **managed** and **unmanaged** solutions. A **managed** solution cannot be modified and can be uninstalled after it is imported. All the components of that solution are deleted by uninstalling the solution.  
 
  When you import an **unmanaged** solution, you add all the components of that solution into your environment. You can’t delete the components by uninstalling the solution.  
@@ -151,17 +151,22 @@ To view a list of component types that can be added to any solution, see [Compon
  This is what you actually see in your environment. The default system solution plus any managed solutions, plus any unmanaged customizations you have applied.  
 
 <a name="BKMK_ManagedProperties"></a>   
-### Managed properties  
+## Managed properties  
  Some components can’t be customized. These components in the system solution have metadata that prevents you from customizing them. These are called **managed properties**. The publisher of a managed solution can also set the managed properties to prevent you from customizing their solution in ways they don’t want you to.  
 
 <a name="BKMK_Dependencies"></a>   
-### Solution dependencies  
+## Solution dependencies  
  Because of the way that managed solutions are layered, some managed solutions can be dependent on solution components in other managed solutions. Some solution publishers will take advantage of this to build solutions that are modular. You may need to install a “base” managed solution first and then you can install a second managed solution that will further customize the components in the base managed solution. The second managed solution depends on solution components that are part of the first solution.  
 
  The system tracks these dependencies between solutions. If you try to install a solution that requires a base solution that isn’t installed, you won’t be able to install the solution. You will get a message saying that the solution requires another solution to be installed first. Similarly, because of the dependencies, you can’t uninstall the base solution while a solution that depends on it is still installed. You have to uninstall the dependent solution before you can uninstall the base solution.  
+ 
+## Solution publisher prefix 
+
+By default, the solution you will work with in Power Apps will be the **Common Data Services Default Solution** which is associated with the **Common Data Service Default Publisher**. The default customization 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 for your organization will have this prepended to the names used to uniquely identify the items. 
+
+We recommend that you change the solution publisher prefix so that it will be more meaningful. More information: [Change the solution publisher prefix](change-solution-publisher-prefix.md)
 
-  
-## Next steps  
+### Next steps  
 [Import, update, and export solutions](import-update-export-solutions.md) <br/>
 [Navigate to a specific solution](navigate-specific-solution.md)