Merge pull request #6487 from MicrosoftDocs/main

pushing to live

Author: mduelae

powerapps-docs/maker/common/wrap/overview.md

@@ -5,7 +5,7 @@ author: larryk78
 ms.topic: article
 ms.custom: canvas
 ms.reviewer: tapanm
-ms.date: 05/31/2022
+ms.date: 06/08/2022
 ms.subservice: canvas-maker
 ms.author: lknibb
 search.audienceType: 
@@ -111,7 +111,6 @@ Container in App Center to store the built packages for mobile app distribution.
 | Platform                                         |  OS | Build Output file type |
 |-------------------------------------------------------------|---------------------------|-------------------------------|
 | **iOS** (for distribution using Apple Store)                                                         | Custom                    |  \*.zip                       |
-| **Android** (for distribution using the Google Play Store)         | Custom                    |      \*.aab                   |
 | **Android** (for distribution using all channels except Google Play Store) |  Android                   | \*.apk                       |
 
 ### App Center URL

powerapps-docs/maker/data-platform/EnvironmentVariables.md

@@ -264,7 +264,7 @@ No. While ALM requires Dataverse (or Dynamics 365 for Customer Engagement), use
 
 ### Is there a limit to the number of environment variables I can have?
 
-No. However, the max size of a solution is 29 MB.
+No. However, the max size of a solution is 32 MB. See [Create a solution](/power-apps/maker/data-platform/create-solution)
 
 ### Can environment variable display names and descriptions be localized?
 

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

@@ -2,9 +2,8 @@
 title: "Create a solution in Power Apps | MicrosoftDocs"
 description: "Learn how to create a solution in Power Apps"
 ms.custom: ""
-ms.date: 05/19/2020
+ms.date: 06/08/2022
 ms.reviewer: ""
-
 ms.topic: "how-to"
 author: "Mattp123"
 ms.assetid: e21a4876-08b4-417a-a644-c577a27c5cf1
@@ -20,8 +19,6 @@ search.app:
 ---
 # Create a solution
 
-
-
 To locate and work with just the components you’ve customized, create a solution and do all your customization there. Then, always remember to work in the context of the custom solution as you add, edit, and create components. This makes it easy to export your solution so that it can be backed up or imported to another environment. 
 
 > [!NOTE]
@@ -199,9 +196,14 @@ Start by opening an unmanaged solution you created. Choose the **table** compone
  > [!div class="mx-imgBorder"] 
  > ![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)
 
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/maker/model-driven-apps/create-edit-quick-view-forms.md

@@ -41,7 +41,7 @@ In the example below notice the module that relates to a given lesson within the
 
 > [!NOTE]
 > - Data in quick view form controls can't be edited and they do not support form scripts. 
-> - Because quick view forms are viewed using a quick view control in a form, they do not include header, footer, or navigation areas. Security roles can't be assigned to quick view forms and they can't be activated or deactivated. Subgrids inside quick view forms will also not display a command bar.
+> - Because quick view forms are viewed using a quick view control in a form, they do not include header, footer, or navigation areas. Security roles can't be assigned to quick view forms and they can't be activated or deactivated.
   
 <a name="BKMK_CreateQFV"></a>