Merge branch 'main' of https://github.com/MicrosoftDocs/powerapps-docs-pr into mg-email-download

Author: gandhamm

powerapps-docs/developer/data-platform/org-service/queryexpression/aggregate-data.md

@@ -1,16 +1,17 @@
 ---
 title: Aggregate data using QueryExpression
 description: Learn how to use QueryExpression to retrieve aggregated data from Microsoft Dataverse.
-ms.date: 05/12/2024
+ms.date: 04/11/2025
 ms.reviewer: jdaly
 ms.topic: how-to
-author: pnghub
+author: olegovanesyan
 ms.subservice: dataverse-developer
-ms.author: gned
+ms.author: olegov
 search.audienceType: 
   - developer
 contributors:
  - JimDaly
+ - daryllabar
 ---
 # Aggregate data using QueryExpression
 
@@ -56,6 +57,7 @@ The types of aggregation you can do are members of the [XrmAggregateType enum](x
 Note the following points:
 
 - Null values aren't considered when calculating aggregate values.
+- Aggregated data is returned as an [AliasedValue](xref:Microsoft.Xrm.Sdk.AliasedValue).
 - You can use data from tables joined using the [LinkEntity class](xref:Microsoft.Xrm.Sdk.Query.LinkEntity).
 - You can apply filters to limit the results as with any query.
 
@@ -65,7 +67,7 @@ Let's say you have 10 account records with the following data:
 
 |Number of Employees|Name|Address 1 City|Created On|
 |---------|---------|---------|---------|
-|NULL|Example Account|NULL|8/25/2023|
+|NULL|Example Account|NULL|8/27/2023|
 |1,500|Contoso Pharmaceuticals (sample)|Redmond|3/25/2023|
 |2,700|Fabrikam, Inc. (sample)|Lynnwood|3/25/2023|
 |2,900|Blue Yonder Airlines (sample)|Los Angeles|3/25/2023|
@@ -142,6 +144,8 @@ Group the results of an aggregate query by adding an [XrmAttributeExpression](xr
 
 When grouping, you should specify a [QueryExpression.Orders](xref:Microsoft.Xrm.Sdk.Query.QueryExpression.Orders) with an [OrderExpression](xref:Microsoft.Xrm.Sdk.Query.OrderExpression) that has the [Alias property](xref:Microsoft.Xrm.Sdk.Query.OrderExpression.Alias) set to the alias of the group.
 
+If a grouped by value is null, it doesn't appear in the results.
+
 
 For example the following query returns the sum of employees, and count by city:
 

powerapps-docs/maker/TOC.yml

@@ -63,6 +63,8 @@
         href: ../user/use-copilot-model-driven-apps.md
       - name: Use Copilot to visualize data in a view (preview)
         href: ../user/visualize-data-in-copilot.md
+      - name: Use Copilot case summary in model-driven apps
+        href: ../user/copilot-case-summary.md       
     - name: Navigation and basics
       items:
       - name: Basic navigation

powerapps-docs/maker/canvas-apps/add-custom-copilot.md

@@ -5,7 +5,7 @@ author: mduelae
 ms.topic: conceptual
 ms.custom: canvas
 ms.reviewer: 
-ms.date: 4/8/2025
+ms.date: 4/10/2025
 ms.subservice: canvas-maker
 ms.author: mkaur
 search.audienceType: 
@@ -20,7 +20,7 @@ contributors:
 You can integrate a custom Copilot created in Microsoft Copilot Studio and enable it for your canvas app. This lets users interact with Copilot to ask questions about the data in your app. With just a few simple steps, you can embed a custom Copilot across all your canvas app screens without changing the app's design.
 
 > [!IMPORTANT]
-> - You can only use this feature on mobile devices. For web scenarios, use [Copilot control for canvas apps](../../maker/canvas-apps/add-ai-copilot.md). 
+> - This feature is available only on mobile devices. For web scenarios, this feature will be deprecated by September 2025. If you're running a canvas apps in a web browser, use the [Copilot control for canvas apps](../../maker/canvas-apps/add-ai-copilot.md) instead.
 > - This is a preview feature.
 > - Preview features aren't meant for production use and might have restricted functionality. These features are subject to [supplemental terms of use](https://go.microsoft.com/fwlink/?linkid=2189520), and are available before an official release so that customers can get early access and provide feedback.
 

powerapps-docs/maker/common/faq-plan-designer.md

@@ -4,7 +4,7 @@ description: FAQ that discusses the Power Apps the Plan designer and the key con
 author: norliu
 contributors: mduelae 
 ms.topic: conceptual
-ms.date: 4/03/2025
+ms.date: 4/10/2025
 ms.author: norliu
 ms.reviewer: mkaur
 ms.collection: 
@@ -35,7 +35,6 @@ We evaluate the feature both qualitatively and quantitatively. To assess the qua
 - Preview features aren’t meant for production use and might have restricted functionality. These features are available before an official release so that customers can get early access and provide feedback. For more information, see preview terms.
 - This capability is powered by Azure OpenAI Service.
 - This capability can be subject to usage limits or capacity throttling.
-- This feature doesn’t support non-English language input.
 - This feature allows maximum input size of 4k tokens, including both text and images. (~ 3,000 words if your input only contains text)
 
 ## What operational factors and settings allow for effective and responsible use of the Plan designer?

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

@@ -50,6 +50,8 @@ Wrap offers several benefits, effectively addressing challenges like increasing
 
 1. **Sovereign cloud**: Wrap is currently not supported in the sovereign cloud.
 
+1. **Full Image View**: Offline-enabled Wrap apps support viewing images as thumbnails but don't currently support viewing images in full view. 
+
 ### See also
 
 - [Troubleshoot issues with the wrap feature in Power Apps](/troubleshoot/power-platform/power-apps/manage-apps-and-solutions/wrap-issues)

powerapps-docs/maker/data-platform/data-retention-faq.yml

@@ -4,7 +4,7 @@ metadata:
   description: Get answers to frequently asked questions about long term retention with Dataverse.
   author: Mattp123
   ms.search.keywords: 
-  ms.date: 09/23/2024
+  ms.date: 04/11/2025
   ms.author: matp
   ms.reviewer: 
   contributors: gned
@@ -72,7 +72,7 @@ sections:
    
    - question: In which regions is Dataverse long term retention available? 
      answer: | 
-       The feature is currently available in all public cloud regions and GCC. GCC High and DOD aren't currently supported.  
+       The feature is currently available in all public cloud regions. GCC, GCC High, and DOD aren't currently supported.  
 
    - question: Can data be moved from Dataverse long term store to my own data lake?
      answer: |

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

@@ -1,7 +1,7 @@
 ---
 title: "Set a preferred solution | MicrosoftDocs"
 description: "Set your preferred solution in Power Apps."
-ms.date: 11/13/2024
+ms.date: 04/09/2025
 ms.topic: conceptual
 author: Mattp123
 ms.subservice: dataverse-maker
@@ -16,14 +16,20 @@ ms.custom:
 ---
 # Set the preferred solution
 
-By default, unless already in the context of an unmanaged solution, all solution components are stored in the solution named Common Data Services Default Solution. Because there's no separation of components between makers and the Common Data Services Default Solution can't be exported for import to other environments, this typically isn't the best model.
+By default, unless you're already in the context of an unmanaged solution when you create an object, all solution objects are stored in the solution named Common Data Services Default Solution. For most situations, you don't want to create your solution objects in either of the two Dataverse system solutions, which are the Common Data Services Solution and the Default Solution. This article explains why using the system solutions is discouraged and provides step-by-step instructions to set and manage your preferred solution.
 
-Using preferred solutions is a way to set which solution will support each maker's edits that happen anywhere in Power Apps. It enables makers to view and update which solution they're using. After you set your preferred solution, you can create components in the solution you specify and those components will automatically be in that solution so that you control the components within the solution. Then, you can export your preferred solution and import the solution to other Microsoft Dataverse environments.
+## Why not create your objects in the system solutions?
+
+There are a few reasons you *shouldn't* create your solution objects in either the Common Data Services Solution and the Default Solution:
+
+- There's no control over the separation of solution objects between makers. All objects can be viewed from the Default Solution and the Common Data Services Solution is the default solution so other makers can and likely are using it.
+- The Default Solution can't be exported for import to other environments.
+- You can't change the solution publisher for the Default Solution. Additionally, since the solutions already exist, you can't change the solution publisher prefix for either system solutions. More information: [Solution publisher](create-solution.md#solution-publisher)
+
+Using preferred solutions is a way to determine which solutions contain each maker's edits that occur in Power Apps. Setting the preferred solution enables makers to view and update which solution they're using. After you set your preferred solution, you can create objects in the solution you specify and those objects will automatically be in that solution so that you control the objects within the solution. Then, you can export your preferred solution and import the solution to other Microsoft Dataverse environments.
 
 > [!NOTE]
->
-> - When your preferred solution isn't set, by default, the **Common Data Services Default Solution** is your preferred solution. If **Common Data Services Default Solution** isn't available, the solution named **Default Solution** is used as your preferred solution. You can change this to your desired solution by following the steps in this article. For more information about the **Common Data Services Default Solution** and **Default Solution**, go to [Default solutions](solutions-overview.md#default-solutions).
-> - The environment setting to enable or disable this feature is no longer available now that preferred solution is generally available.
+> When your preferred solution isn't set, by default, the **Common Data Services Default Solution** is your preferred solution. If **Common Data Services Default Solution** isn't available, the solution named **Default Solution** is used as your preferred solution. You can change this to your desired solution by following the steps in this article. For more information about the **Common Data Services Default Solution** and **Default Solution**, go to [Default solutions](solutions-overview.md#default-solutions).
 
 ## Prerequisites
 
@@ -44,15 +50,15 @@ Once your preferred solution is set, notice the **preferred solution** indicator
 You can delete your preferred solution or a preferred solution that other makers have also set as their preferred solution.
 
 > [!WARNING]
-> When you delete a preferred solution you receive a warning that includes the fallback default solution and the number of other makers who are using the same solution. Delete an active solution only when you're sure it won't impact your work or the work of other makers.
+> When you delete a preferred solution, you receive a warning that includes the fallback default solution and the number of other makers who are using the same solution. Delete an active solution only when you're sure it won't impact your work or the work of other makers.
 > 
 > :::image type="content" source="media/delete-preferred-solution.png" alt-text="Delete a preferred solution warning":::
 
 ## Limitations
 
 - You can't set or view the preferred solution in the classic solution explorer.
 - Components that are created in the classic solution explorer won't go into the preferred solution.
-- Preferred solution currently doesn't work with Dataverse for Teams,cards, dataflows, AI Builder, chatbots, connections, gateways, custom connectors, Power Automate flows (limited), and canvas apps created from image or a Figma design.
+- Preferred solution currently doesn't work with Dataverse for Teams, cards, dataflows, AI Builder, chatbots, connections, gateways, custom connectors, Power Automate flows (limited), and canvas apps created from image or a Figma design.
 - When a component is already part of an existing unmanaged solution, it will still be added to the preferred solution.
 
 ## See also

powerapps-docs/maker/data-platform/set-managed-properties-for-field.md

@@ -1,8 +1,8 @@
 ---
-title: "Set managed properties for columns in Power Apps | MicrosoftDocs"
-description: "Learn how to set managed properties for a column"
+title: "Set managed properties for columns in Power Apps"
+description: "Learn how to set managed properties for a column in Microsoft Dataverse."
 ms.custom: ""
-ms.date: 11/13/2024
+ms.date: 04/10/2025
 ms.reviewer: ""
 ms.suite: ""
 ms.tgt_pltfrm: ""
@@ -22,30 +22,29 @@ search.audienceType:
 ---
 # Set managed properties for columns
 
-Managed properties only apply when you include columns in a managed solution and import the solution into another environment. These settings allow a solution maker to have some control over the level of customization that people who install their managed solution can have when they customize this column.
+Managed properties only apply when you export columns in a managed solution and import the solution into another environment. These settings allow a solution maker to have some control over the level of customization that people who install their managed solution can have when they customize this column.
 
 To view and set managed properties for a column, follow these steps:
 
 1. Sign into [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc) and select **Solutions** from the left navigation. [!INCLUDE [left-navigation-pane](../../includes/left-navigation-pane.md)]
-1. Open the solution, and then on the command bar select **Switch to classic**.
-1. Expand **Entities**, expand the table you want, and then select **Fields**.
+1. Open the solution, open the table you want, and then open the **Columns** area.
 1. Select the column you want.
-1. On the command bar select **More Actions**, and then select **Managed Properties**.  
+1. On the command bar select **More Actions**, and then select **Managed properties**.  
 1. Select the [managed properties options](#managed-properties-options) you want, and then select **Set**.
 
 ## Managed properties options
 
-The **Can be customized** option controls all the other options. If this option is `False`, none of the other settings apply. When it is `True`, you can specify the other customization options.  
+The **Allow customizations** option controls all the other options. If this option is `False`, none of the other settings apply. When it is `True`, you can specify the other customization options.  
 
  If the column is customizable, you set the following options to `True` or `False`.  
 
 - **Display name can be modified**  
 
 - **Can change requirement level**  
 
-- **Can change Additional Properties**  
+- **Can change additional properties**  
 
-These options are self-explanatory. If you set all the individual options to `False`, you might as well set **Can be customized** to `False`.  
+These options are self-explanatory. If you set all the individual options to `False`, you might as well set **Allow customizations** to `False`.  
 
 ## Next steps
 

powerapps-docs/maker/model-driven-apps/manage-commands-in-solutions.md

@@ -14,22 +14,28 @@ search.audienceType:
 
 # Manage commands in solutions
 
-Unlike classic commands, modern commands are treated the same as other solution components and support core solution behaviors. You can also edit existing modern commands from within a solution.
+Unlike classic commands, modern commands are treated the same as other solution objects and support core solution behaviors. You can also edit existing modern commands from within a solution.
+
+To add commands to a solution, you add the solution objects that depend on your command actions:
+
+- Modern commands are a table component. When you add a command to a solution, you must add the command component. In this screenshot there's one JavaScript and one Power Fx command for the custom Classroom table that can be added as a specific object to a solution for export.
+   :::image type="content" source="media/commanddesigner-add-to-solution.png" alt-text="Add a command table component to a solution":::
+- Power Fx commands use a Dataverse component library. Add the component library to your solution if you plan to export it.
+- JavaScript commands use a web resource. Add the web resource that includes the underlying JavaScript to run your command to the solution if you plan to export it.
+
+More information: [Add an existing component to a solution](../data-platform/create-solution.md#add-an-existing-component-to-a-solution)
 
 Modern commanding provides these benefits when you work with solutions:
-- Add solution components that depend on your command actions.
-- Block commands from being customized by using managed properties.
-- View dependencies related to your modern command components.
-- Troubleshoot by viewing which solutions modified the component and when using solution layers.
-- Remove any unmanaged customizations if in an unhealthy state.
-- Add or remove command components from a solution.
+
+- Block commands from being customized by using managed properties. Open the table, select **Commands**, select the command, and then on the command bar select **Advanced** > **Managed properties** to disable **Allow customizations**.
+- View dependencies related to your modern command components. More information: [View dependencies for a component in Power Apps](../data-platform/view-component-dependencies.md)
+- Troubleshoot by viewing which solutions modified the component and when using solution layers. More information: [Solution layers](../data-platform/solution-layers.md)
+- Remove any unmanaged customizations if in an unhealthy state. More information: [Remove an unmanaged layer](../data-platform/solution-layers.md#remove-an-unmanaged-layer)
 - Segment solutions and build minor updates or patches that include your modern command components.
-    > [!div class="mx-imgBorder"]
-    > ![Clone a patch](media/CommandDesigner-clone-a-patch.png "Clone a patch")
-- Modern command components work with solution upgrade so you can delete components by importing a new version.
-- Standardized localization via export/import translations.
+- Modern command components work with solution upgrade so you can delete components by importing a new version. [Upgrade or update a solution](../data-platform/update-solutions.md)
+- Standardized localization via export/import translations. More information: [Translate label text](../data-platform/translate-entity-label-text.md)
 
-### See also
+## Related articles
 
 [Modern commanding overview](command-designer-overview.md)