Merge branch 'main' into ChrisGarty-patch-6

Author: Mattp123

powerapps-docs/developer/data-platform/build-and-package.md

@@ -1,7 +1,7 @@
 ---
 title: Build and package plug-in code
 description: Learn about building plug-in code into assemblies and packages for later registration and upload to the Microsoft Dataverse service.
-ms.date: 02/26/2024
+ms.date: 02/29/2024
 ms.reviewer: pehecke
 ms.topic: article
 author: divkamath
@@ -32,15 +32,15 @@ Your assembly may include multiple plug-in classes (or types) and even custom wo
 
 ### Signed assemblies are required
 
-Assemblies must be signed before they can be registered with Dataverse only if you are not using the [dependent assemblies](#dependent-assemblies) capability. You can use the Visual Studio **Signing** tab in your project's properties or the [Sn.exe (Strong Name Tool)](/dotnet/framework/tools/sn-exe-strong-name-tool) command to sign the assembly.
+Assemblies must be signed before they can be registered with Dataverse only if you aren't using the [dependent assemblies](#dependent-assemblies) capability. You can use the Visual Studio **Signing** tab in your project's properties or the [Sn.exe (Strong Name Tool)](/dotnet/framework/tools/sn-exe-strong-name-tool) command to sign the assembly.
 
 ### Dependency on the CoreAssemblies NuGet package
 
-Adding the `Microsoft.CrmSdk.CoreAssemblies` NuGet package to your project includes the required Dataverse assembly references in your project, but it doesn't upload these assemblies along with your plug-in assembly as these assemblies already exist in the server's sandbox run-time where your code will execute.
+Adding the `Microsoft.CrmSdk.CoreAssemblies` NuGet package to your project includes the required Dataverse assembly references in your project, but it doesn't upload these assemblies along with your plug-in assembly as these assemblies already exist in the server's sandbox run-time where your code executes.
 
 ### Where to go next
 
-If you are interested in learning about or using dependent assemblies, continue reading the next section in this article. If not, proceed to [Register a plug-in](register-plug-in.md).
+If you're interested in learning about or using dependent assemblies, continue reading the next section in this article. If not, proceed to [Register a plug-in](register-plug-in.md).
 
 ## Dependent assemblies
 
@@ -68,7 +68,7 @@ When you register individual plug-in assemblies without the dependent assemblies
 
 > [!IMPORTANT]
 > If you sign your assemblies, be aware that signed assemblies cannot use resources contained in unsigned assemblies. If you sign your plug-in assemblies or any dependent assembly, all the assemblies that those assemblies depend on must be signed.
-> 
+>
 > If any signed assemblies depend on unsigned assemblies, you will get an error similar to the following: Could not load file or assembly \<AssemblyName>, Version=\<Version>, Culture=neutral, PublicKeyToken=null or one of its dependencies. A strongly-named assembly is required.
 
 ### Dependent assemblies limitations
@@ -77,15 +77,47 @@ The following limitations apply when using plug-in dependent assemblies.
 
 - [Workflow extensions](workflow/workflow-extensions.md), also known as *custom workflow activities* aren't supported when using the dependent assemblies capability.
 - On-premises environments aren't supported.
-- Un-managed code isn't supported. You can't include references to unmanaged resources.
+- Un-managed code isn't supported. You can't include references to un-managed resources.
 
 ## Creating a plug-in package
 
-Your plug-in assembly plus any required dependent assemblies can be placed together in a NuGet package and then registered and uploaded to the Dataverse server. You do not need to create a package if your plug-in project does not require any dependent assemblies at run-time, other than what ships in the Microsoft.CrmSdk.CoreAssemblies NuGet package.
+Your plug-in assembly plus any required dependent assemblies can be placed together in a NuGet package and then registered and uploaded to the Dataverse server. You don't need to create a package if your plug-in project doesn't require any dependent assemblies at run-time, other than what ships in the Microsoft.CrmSdk.CoreAssemblies NuGet package.
 
 <!-- Add correct links when available -->
 Instructions for creating a plug-in package using an interactive tool can be found in these separate how-to's: [Create and register a plug-in package using PAC CLI](/power-platform/developer/howto/cli-create-package), [Create and register a plug-in package using Visual Studio](/power-platform/developer/howto/vs-create-package).
 
+## All projects must be in the SDK style
+
+A plug-in package must only contain custom assemblies that are built from a project file in a specific format known as the *SDK style*. Failure to follow this rule results in an error ("file can not be found") when attempting to register the package using the Plug-in Registration tool.
+
+> [!IMPORTANT]
+> All MSBuild projects, where the resulting compiled assembly is to be added to a plug-in package, must be in the "SDK style" format.
+
+An SDK style project is one where the contents of the project's .csproj file contains the following line of code: `<Project Sdk="Microsoft.NET.Sdk">`.
+
+When you create a plug-in project using one of our tools, for example the Power Platform CLI `pac plugin init` command, the plug-in project file is in the correct format. Here's an example of such a project file.
+
+```makefile
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <TargetFramework>net462</TargetFramework>
+    <PowerAppsTargetsPath>$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v$(VisualStudioVersion)\PowerApps</PowerAppsTargetsPath>
+    <AssemblyVersion>1.0.0.0</AssemblyVersion>
+    <FileVersion>1.0.0.0</FileVersion>
+    <ProjectTypeGuids>{4C25E9B5-9FA6-436c-8E19-B395D2A65FAF};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids>
+  </PropertyGroup>
+  ...
+</Project>
+```
+
+If you're adding another project to the Visual Studio solution, say a class library project, you can create an SDK style project by following these steps.
+
+1. In Visual Studio, add the new project to your solution using a .NET or .NET Standard template. Do not target .NET Framework.
+1. Edit the project file by right-clicking on the project name in Solution Explorer and select **Edit project file**, or simply open the project's .csproj file in a separate editor.
+1. You should see the line `<Project Sdk="Microsoft.NET.Sdk">` in the project file. Change the TargetFramework property to be `<TargetFramework>net462</TargetFramework>` and save the file.
+1. Verify your solution builds, and you're done.
+
 ### Don't depend on System.Text.Json
 
 Because the Microsoft.CrmSdk.CoreAssemblies NuGet package has a [dependency](https://www.nuget.org/packages/Microsoft.CrmSdk.CoreAssemblies#dependencies-body-tab) on System.Text.Json, you're able to refer to [System.Text.Json](xref:System.Text.Json) types at design time. However, the System.Text.Json.dll file in the sandbox run-time can't be guaranteed to be the same version that you reference in your project. If you need to use `System.Text.Json`, you should use the dependent assembly feature and explicitly include it in your NuGet package.

powerapps-docs/maker/TOC.yml

@@ -460,6 +460,8 @@
             href: ./canvas-apps/use-line-pie-bar-chart.md
           - name: Add multimedia
             href: ./canvas-apps/add-images-pictures-audio-video.md
+          - name:  Use Copilot answer control (preview)
+            href: ./canvas-apps/copilot-answer-control-overview.md
           - name: "Add mixed reality controls"
             items:
             - name: Mixed reality controls
@@ -540,6 +542,8 @@
               href: ./canvas-apps/controls/modern-controls/modern-controls-badge.md
             - name: Checkbox (preview)
               href: ./canvas-apps/controls/modern-controls/modern-control-checkbox.md
+            - name: Copilot answer (preview) 
+              href: ./canvas-apps/controls/modern-controls/modern-control-copilot-answer.md
             - name: Date picker (preview)
               href: ./canvas-apps/controls/modern-controls/modern-controls-date-picker.md
             - name: Dropdown (preview)

powerapps-docs/maker/canvas-apps/connections/connection-azure-sqldatabase.md

@@ -47,37 +47,41 @@ You can directly call SQL Server stored procedures from Power Fx by turning on t
 
 1. Go to **Settings** > **Upcoming features** > **Preview**.
 1. Search for _stored procedures_.
-1. Turn on the preview switch as shown.
+1. Turn on the preview switch as shown.  (You will need to save and reopen the app.)
 
 :::image type="content" source="media/connection-azure-sqldatabase/previewflag-call-sp-direct.png" alt-text="Screenshot that shows the SQL Server stored procedures toggle set to On.":::
 
-When you add a SQL Server connection to your app, you can now add tables and views or stored procedures.
+When you add a SQL Server connection to your app, you can now add tables and views or stored procedures. This feature also works with secure implicit connections.
 
 :::image type="content" source="media/connection-azure-sqldatabase/tables-views-stored-proc-selector.png" alt-text="Screenshot that shows lists of tables, views, and stored procedures available to be added to your app.":::
 
 If you don't immediately see your stored procedure, it's faster to search for it.
 
 Once you select a stored procedure, a child node appears and you can designate the stored procedure as **Safe to use for galleries and tables**. If you check this option, you can assign your stored procedure as an **Items** property for galleries for tables to use in your app.
 
-Enable this option only if:
+Enable this option **only if**:
 
-1. There are no side effects to calling this procedure on demand, multiple times, whenever Power Apps refreshes the control. When used with an **Items** property of a gallery or table, Power Apps calls the stored procedure whenever the system determines a refresh is needed. You can't control when the stored procedure is called.
-2. The stored procedure returns less than the delegable limit (500/2000) of records. When a table or view is assigned to an **Items** property, Power Apps can control the paging and bring in 100 records at a time, when it needs it. Stored procedures are different and might be pageable through an argument to the stored procedure. But Power Apps can't bring in pages automatically like it can for tables and views. The author must configure pageability.
+1. There are **no side effects** to calling this procedure on demand, multiple times, whenever Power Apps refreshes the control. When used with an **Items** property of a gallery or table, Power Apps calls the stored procedure whenever the system determines a refresh is needed. You can't control when the stored procedure is called.
+2. The amount of data you return in the stored procedure is **modest**. Action calls, such as stored procedures, do not have a limit on the number of rows retrieved. They are not automatically paged in 100 record increments like tabular data sources (tables or views.) So, if the stored procedure returns a lot of data (many thousands of records) then your app may slow down or crash. For performance reasons you should bring in less than 2000 records.
 
 ### Example
 
 When you add a stored procedure, you might see more than one data source in your project.
 
 :::image type="content" source="media/connection-azure-sqldatabase/sqlserver-datasources.png" alt-text="Screenshot that shows SQL data sources.":::
 
-Prefix the stored procedure name with the name of connector associated with it. For example, _DataCardValue3_1.Text_ is from the _DataCard_ connector.
+To use a stored procedure in Power Apps, first prefix the stored procedure name with the name of connector associated with it and the name the stored procedure. 'Paruntimedb.dbonewlibrarybook' in the example illustrates this pattern. Note also that when Power Apps brings the stored procedure in, it concatenates the full name. So, 'dbo.newlibrarybook' becomes 'dbonewlibrarybook'.  
 
-Label the values, for example using a number, as necessary since you're reading from a text value in Power Apps.
+Remember to convert values appropriately as you pass them into your stored procedure as necessary since you're reading from a text value in Power Apps. For example, if you are updating an integer in SQL you must convert the text in the field using 'Value()'.
 
 ![Calling stored procedures directly.](media/connection-azure-sqldatabase/calling-sp-directly.png "Calling stored procedures directly.")
 
 > [!TIP]
-> To use a stored procedure in an **Item** property for a gallery or table, use the stored procedure name where you'd use the table name.
+> To use a stored procedure in an **Item** property for a gallery or table, use the stored procedure name where you'd use the table name. Views do not have primary keys so you will need to supply a key value for record specific operations. You can access the stored procedure after you declare it safe for the UI. Reference the data source name and the the name of the stored procedure followed by 'ResultSets'. You can access multiple results by indexing through list of tables returned.
+>
+```powerapps-dot
+Paruntimedb.dbospshowalllibrarybooks().ResultSets.Table1
+```
 
 ## Known issues
 

powerapps-docs/maker/canvas-apps/controls/modern-controls/modern-control-copilot-answer.md

@@ -0,0 +1,54 @@
+---
+title: Copilot answer modern control in Power Apps
+description: Learn about the details, properties, and examples of the Copilot answer modern control in Power Apps.
+author: yogeshgupta698
+
+ms.topic: reference
+ms.component: canvas
+ms.date: 2/14/2024
+ms.subservice: canvas-maker
+ms.author: yogupt
+ms.reviewer: mkaur
+search.audienceType: 
+  - maker
+contributors:
+  - mduelae
+  - yogeshgupta698
+  
+---
+# Copilot answer modern control in Power Apps (preview)
+
+[This article is pre-release document and is subject to change.]
+
+A control that makers can use to add predefined questions that end users can use to get generated answers.
+
+## Description
+
+Makers can use the Copilot answer control to set predefined questions that end users can use to get generative answers with a single click. The control is optimized for mobile users and is powered by Microsoft Copilot.
+
+## Key properties
+
+**Data source (Items)** – The Copilot answer control only supports Dataverse as the data source. The answer to the question comes from the Dataverse table that you select.
+
+**Views** – A user can select any of the views that are available in the data source.  
+
+**Fields** - Default list of fields available for the table. Users can select **Edit** to see the list of fields. They can also add or modify the fields based on their requirements.  
+
+**Title** – A label that is displayed at the top of the Copilot answer control.  
+
+**Question for Copilot** – This is the question a maker asks the Copilot answer control. The question is used as the prompt to generate a response that is displayed by the answer control that's based on the selected **Data source** property.
+
+
+## Additional properties
+
+**Show answer** – Should the Copilot answer control answer a question when the user clicks on the ‘Arrow’ icon (After sending) or as soon as the control loads when the question is defined in the properties window (Immediate).
+
+**DisplayMode** – Whether the control allows user input (Edit), only displays data (View), or is disabled (Disabled).
+
+**Position** - Whether a control appears or is hidden.
+
+**[X](../properties-size-___location.md)** – The distance between the left edge of a control and the left edge of its parent container (screen if no parent container).
+
+**[Y](../properties-size-___location.md)** – The distance between the top edge of a control and the top edge of the parent container (screen if no parent container).
+
+**[Size](../properties-text.md)** – The size of the control on the canvas

powerapps-docs/maker/canvas-apps/controls/modern-controls/modern-controls-reference.md

@@ -31,6 +31,8 @@ Configure the behavior of a modern control by setting one of its properties. Eac
 
 **[Checkbox](modern-control-checkbox.md)** - Select or clear an option to specify **true** or **false**.
 
+**[Copilot answer (preview)](modern-control-copilot-answer.md)** - A control that makers can use to add predefined questions that end users can use to get generated answers.
+
 **[Date picker](modern-controls-date-picker.md)** - A control that the user can select to specify a date.
 
 **[Dropdown](modern-control-dropdown.md)** – Select a value from the list of items.

powerapps-docs/maker/canvas-apps/copilot-answer-control-overview.md

@@ -0,0 +1,70 @@
+---
+title: Overivew of Copilot answer control for canvas apps
+description: Use the Copilot answer control for canvas app.
+author: mduelae
+ms.topic: conceptual
+ms.custom: canvas
+ms.collection: 
+    - bap-ai-copilot
+    - get started
+ms.reviewer: mkaur
+ms.date: 2/13/2024
+ms.subservice: canvas-maker
+ms.author: arijitba
+search.audienceType: 
+  - maker
+contributors:
+  - mduelae
+---
+
+#  Use Copilot answer control for canvas apps (preview)
+
+[This article is prerelease documentation and is subject to change.]
+
+Makers can use the Copilot answer control to set predefined questions that end users can use to get AI-generated information with a single click. The control is powered by Microsoft Copilot and is designed for mobile users to provide them with immediate answers to frequently asked questions.
+
+:::image type="content" source="media/answer-control/answer-control-shown-on-mobile.png" alt-text="Answers shown on mobile":::
+
+## Enable Copilot answer control for your environment
+
+To use the Copilot answer control in a canvas app, an admin must first turn on the feature, **Allow canvas editors to insert the Copilot answer component, which allows users to receive an AI-powered answer to a predefined data query** in their environment. 
+
+This setting can be found in the [Power Platform admin center](https://admin.powerplatform.microsoft.com) by going to **Environments** > [select an environment] > **Settings** > **Product** > **Features**. For more information, see [Manage feature settings](/power-platform/admin/settings-features#copilot-preview).
+
+:::image type="content" source="media/answer-control/answer-control-enable-by-admin.jpg" alt-text="Turn on Copilot answer control on Power Platform admin center":::
+
+## Add Copilot answer control
+
+With your [canvas app open for editing](edit-app.md) in Power Apps Studio:
+
+1. On the command bar, select **Insert** and then select one of the following options:
+   
+    - **Modern** > **Copilot answer (preview)**
+    - **Classic** > **Copilot answer (preview)**
+      
+    :::image type="content" source="media/answer-control/answer-control-insert.png" alt-text="Insert answer control":::
+
+1. When the **Copilot answer (preview)** control is added to the canvas app, select a data source from the pane. Copilot only supports Dataverse tables.
+
+   :::image type="content" source="media/answer-control/answer-control-select-data-type.png" alt-text="Select data source":::
+
+1. On the control properties pane, select the **Properties** tab.
+
+1. In the properties, enter the **Title**, **Questions for Copilot**, and **Show answer** for the question. You can also edit other control properties as needed.
+
+   :::image type="content" source="media/answer-control/answer-control-properties.png" alt-text="Answer control properties":::
+
+1. When you're done, [save and publish](save-publish-app.md) your app.
+
+## Use Copilot answer control
+
+End users can regenerate responses and provide feedback on the quality of responses.
+
+Follow these steps to see answers generated by the Copilot answer control:
+
+1. Open a canvas app on Power Apps mobile and navigate to the Copilot answer control in your app.
+1. On the Copilot answer control select, **Send**.
+
+    :::image type="content" source="media/answer-control/answer-control-send.png" alt-text="Use Copilot answer control on mobile":::
+
+