Revised for freshness and PII in image

Author: Mattp123

powerapps-docs/maker/data-platform/create-solution.md

@@ -2,7 +2,7 @@
 title: "Create a solution in Power Apps | MicrosoftDocs"
 description: "Learn how to create a solution in Power Apps"
 ms.custom: ""
-ms.date: 06/14/2023
+ms.date: 08/08/2024
 ms.reviewer: ""
 ms.topic: "how-to"
 author: "Mattp123"
@@ -29,29 +29,29 @@ To create a solution:
     |-----------|-----------------|  
     |**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 column. 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. We recommend that you create a publisher for your organization to use consistently across your environments where you will use the solution. See [Solution publisher](#solution-publisher) later in this article. |  
-    |**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.|  
+    |**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 where you'll use the solution. See [Solution publisher](#solution-publisher) later in this article. |  
+    |**Version**|Enter a number for the version of your solution. This is only important if you export your solution. The version number is included in the file name when you export the solution.|  
 
 3.  Select **Save**.  
 
- After you save the solution, you may wish to add information to columns that aren’t required. These steps are optional. Use the **Description** column to describe the solution and choose an HTML web resource as a **Configuration Page** for the solution. The configuration page is typically used by ISVs who distribute solutions. When this is set, a new **Configuration** node appears below the **Information** node to display this web resource. Developers will use this page to include instructions or controls to allow you to set configuration data or launch their solution.  
+ After you save the solution, you might wish to add information to columns that aren’t required. These steps are optional. Use the **Description** column to describe the solution and choose an HTML web resource as a **Configuration Page** for the solution. The configuration page is typically used by ISVs who distribute solutions. When this is set, a new **Configuration** node appears below the **Information** node to display this web resource. Developers use this page to include instructions or controls to allow you to set configuration data or launch their solution.  
 
 <a name="BKMK_AddSolutionComponents"></a>
 
 ## Add solution components
 
- After you’ve created your solution, it won’t contain any solution components. You can create new components to be added to the solution or add existing components to your new solution.
+After you’ve created your solution, it won’t contain any solution components. You can create new components to be added to the solution or add existing components to your new solution.
 
- ### Create components in a solution
+### Create components in a solution
 
- You can use the **New** command to create different types of components. This takes you to a different create experience depending on the component type that you choose. After you finish creating the component, it will be added to the solution. 
+You can use the **New** command to create different types of components. This takes you to a different create experience depending on the component type that you choose. After you finish creating the component, it will be added to the solution. 
 
 > [!div class="mx-imgBorder"]  
 > ![Create new component in a solution.](media/solution-new-component.PNG "Create new component in a solution")  
  
- ### Add an existing component to a solution
+### Add an existing component to a solution
 
- With solutions that are unmanaged and not the default one, you can use the **Add existing** command to bring in components that aren’t already in the solution.  
+With solutions that are unmanaged and not the default one, you can use the **Add existing** command to bring in components that aren’t already in the solution.  
 
 > [!div class="mx-imgBorder"]  
 > ![Add existing component to a solution.](media/solution-add-existing-component.PNG "Add existing component to a solution")  
@@ -61,22 +61,11 @@ To create a solution:
   
 When you add an existing table, rather than select **Include all components** or **Include table metadata**, use the **Select components** option to only add the table components that have been updated. With solution segmentation, you export solution updates with selected table assets, such as table columns, forms, and views, rather than entire tables with all the assets. [Create a segmented solution with table assets](#create-a-segmented-solution-with-table-assets)
 
- Many of the customizations you’ll want to do will involve tables. You can use the **table** filter to show a list of all the tables in the current solution that can be customized in some way. Once you drill into a table, you can see the components that are part of the table as shown with the account table in the following screenshot. 
+Many of the customizations you’ll want to do involve tables. You can use the **table** filter to show a list of all the tables in the current solution that can be customized in some way. Once you drill into a table, you can see the components that are part of the table as shown with the account table in the following screenshot. 
 
 > [!div class="mx-imgBorder"]  
 > ![Demo solution showing expanded account table.](media/solution-entity-account.png "Demo solution showing expanded account table")  
   
-<!--
-When you do this you may see a **Missing Required Components** dialog.  
-   
- ![Add Required Components Dialog.](media/crm-itpro-cust-addrequiredcomponents.PNG "Add Required Components Dialog")  
-  
- This dialog alerts you that the solution component has dependencies on other solution components. If you select **No, do not include required components**, the solution may fail if you import it into another organization where all those required components do not exist. If the solution import succeeds, the behavior in the other solution may not be identical as the original organization because the components are configured differently than those in the source solution.  
-  
-When you select table components, we recommend that you use solution segmentation so that you only include table components that are new or updated when you distribute solution updates. With solution segmentation, you work in a solution with selected table assets, such as table columns, forms, and views, rather than entire tables with all the assets. More information: [Use segmented solutions](use-segmented-solutions-patches-simplify-updates.md)
-  
- If you don’t intend to export the solution, or if you only intend to export it as an unmanaged solution and import it back into the same organization, it isn’t necessary to include required components. If you ever export the solution you’ll see another warning indicating that some required components are missing. If you are only going to import this solution back into the same organization, it is OK to disregard this warning. The steps to edit application navigation or the ribbon without using a third-party editing tool expect that you’ll export the solution back into the same organization.-->  
-
 ## Publish changes 
 
 When you make unmanaged changes in an environment, some components, such as forms, tables, model-driven apps, site maps, and views are saved in an unpublished state. The publish action promotes these changes to an active state and makes them available to end users and for export. 
@@ -95,6 +84,7 @@ When you make unmanaged changes in an environment, some components, such as form
 >  Preparing customizations may take some time. If you see a message that the browser page has become unresponsive, wait for the page to become responsive, and don't close it.  
 
 ## Solution publisher
+
 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. 
 
 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. For more information about the solution publisher, see [Solution publisher](/power-platform/alm/solution-concepts-alm#solution-publisher) in the Power Platform ALM guide.
@@ -117,7 +107,7 @@ The solution publisher indicates who developed the app. For this reason, you sho
 4. Select **Save and Close**.
 
 > [!NOTE]
-> Do not use _upgrade as part of the solution name.  _upgrade is an internal reserved word for the solution [upgrade  process](/power-apps/maker/data-platform/update-solutions#apply-the-upgrade-or-update-in-the-target-environment). 
+> Don't use _upgrade as part of the solution name.  _upgrade is an internal reserved word for the solution [upgrade  process](/power-apps/maker/data-platform/update-solutions#apply-the-upgrade-or-update-in-the-target-environment). 
 
 ### Change a solution publisher
 
@@ -134,7 +124,7 @@ Use solution segmentation so that you only include table components that are upd
 
 ### Create a segmented solution with table assets
 
- To create a segmented solution, start with creating an unmanaged solution and add only the components that you've updated. The wizard-like setup takes you step by step through the process of adding table assets. 
+To create a segmented solution, start with creating an unmanaged solution and add only the components that you've updated. The wizard-like setup takes you step by step through the process of adding table assets. 
 
 For example, imagine that you've created a new custom table that doesn't exist in any other environment named *Custom table* and also added a new column named *topten* for the account table. To create a segmented solution, follow these steps. 
 
@@ -162,7 +152,8 @@ For example, imagine that you've created a new custom table that doesn't exist i
 
 7. Select **Add** to add the components to the solution. 
 
-### Create a segmented solution using solution explorer  
+### Create a segmented solution using solution explorer
+
 The following illustrations provide an example of creating a segmented solution by choosing table assets from the `Account`, `Case`, and `Contact` tables.  
 
 > [!NOTE]
@@ -177,7 +168,7 @@ Start by opening an unmanaged solution you created. Choose the **table** compone
 
  ![Select solution's components.](media/solution-segmentation-select-components-admin.png "Select solution's components.")  
 
- Follow the wizard. In Step 1, starting in alphabetical order, select the assets for the first table, the `Account` table, as shown here.  
+Follow the wizard. In Step 1, starting in alphabetical order, select the assets for the first table, the `Account` table, as shown here.  
 
  ![Start the wizard.](media/solution-segmentation-wizard-starts-admin.png "Start the wizard.")  
 
@@ -199,11 +190,13 @@ Start by opening an unmanaged solution you created. Choose the **table** compone
  > ![Solution with tables.](media/solution-segmentation-solution-entities-admin.png "Solution with tables.")
 
 ### Limitations
+
 - Solution size is limited to 32 MB.
 - Number of solutions is limited by Microsoft Dataverse capacity.
 - Number of objects in a solution is limited by Dataverse capacity.
 
 ### See also
+
  [Use solutions](./solutions-overview.md) <br />
 [For developers: Create, export, or import an unmanaged solution](/power-platform/alm/solution-api#create-export-or-import-an-unmanaged-solution)