Merge pull request #8360 from MicrosoftDocs/main

update working

Author: mduelae

powerapps-docs/developer/data-platform/bulk-operations-elastic-tables.md

@@ -14,9 +14,9 @@ contributors:
 
 [!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
 
-Often applications need to ingest large amount of data into Dataverse in a short amount of time. Dataverse has a group of messages that are designed to achieve high throughput. With elastic tables, the throughput can be much higher.
+Often applications need to ingest large amount of data into Dataverse in a short amount of time. Dataverse has a group of messages that are designed to achieve high throughput. With elastic tables, the throughput can be higher.
 
-Bulk operations are optimized for performance when executing multiple write operations on the same table by taking a batch of rows as input in a single write operation. For elastic tables, we recommend sending 100 items in a batch. Multiple bulk operation can be run in parallel to achieve high throughput. More information [Send parallel requests](send-parallel-requests.md)
+Bulk operations are optimized for performance when executing multiple write operations on the same table by taking a batch of rows as input in a single write operation. For elastic tables, we recommend sending 100 items in a batch. Multiple bulk operations can be run in parallel to achieve high throughput. More information [Send parallel requests](send-parallel-requests.md)
 
 Elastic tables currently support the following messages for bulk operations:
 
@@ -183,6 +183,32 @@ public static OrganizationResponse DeleteMultiple(IOrganizationService service)
 }
 ```
 
+## Exception handling for elastic tables
+
+Unlike standard tables, an error within a bulk operation with an elastic table doesn't roll back the entire request. It's possible for the operation to partially succeed and you can detect which records have failed from the ErrorDetails.
+
+
+When you use the SDK, a [FaultException](xref:System.ServiceModel.FaultException%601) of type [OrganizationServiceFault](xref:Microsoft.Xrm.Sdk.OrganizationServiceFault) is thrown if a failure occurs. You can get the status of each record using the following code.
+
+```csharp
+if (ex.Detail.ErrorDetails.TryGetValue("Plugin.BulkApiErrorDetails", out object errorDetails))
+{
+   List<BulkApiErrorDetail> bulkApiErrorDetails = JsonConvert.DeserializeObject<List<BulkApiErrorDetail>>(errorDetails.ToString());
+}
+
+public class BulkApiErrorDetail
+{
+   public int RequestIndex { get; set; }
+   public string Id { get; set; }
+   public int StatusCode { get; set; }
+}
+```
+
+When using Web API, you need to pass the `Prefer` header with value `odata.include-annotations=*` or `odata.include-annotations=Microsoft.PowerApps.CDS.ErrorDetails.*`, which gives the status of each record. More information: [Include more details with errors](webapi/compose-http-requests-handle-errors.md#include-more-details-with-errors)
+
+> [!NOTE]
+> You can see the errors in the above format only when the errors have occurred while writing data and cannot capture errors occurred in Pre and Post plugins. More information: [Handling Exceptions](write-plugin-multiple-operation.md#handling-exceptions).
+
 ### See also
 
 [Use elastic tables](elastic-tables.md)<br />

powerapps-docs/developer/data-platform/files-images-overview.md

@@ -35,7 +35,7 @@ Dataverse provides several different ways to save binary data representing files
 
 ## Block certain types of files
 
-You can block the types of files that can be uploaded by the extension or mime type.
+You can block the types of files that can be uploaded by the extension or MIME type.
 
 ### Block files by extension
 
@@ -111,9 +111,9 @@ When anyone tries to upload a file using one of the blocked types, the following
 > Number: `-2147205623`<br />
 > Message: `The attachment is either not a valid type or is too large. It cannot be uploaded or downloaded.`
 
-### Block or allow certain mime types
+### Block or allow certain MIME types
 
-You can block or allow upload of files based on mime types. More Information: [Mime Type Validation](/power-platform/admin/settings-privacy-security#mime-type-validation).
+You can block or allow upload of files based on MIME types. More Information: [Mime Type Validation](/power-platform/admin/settings-privacy-security#mime-type-validation).
 
 You can also query and modify this data programmatically. It's stored in the [Organization.BlockedMimeTypes](reference/entities/organization.md#BKMK_BlockedMimeTypes) and [Organization.AllowedMimeTypes](reference/entities/organization.md#BKMK_AllowedMimeTypes) columns. There's only one row in the organization table. You can use the SDK or Web API to query this data:
 
@@ -165,15 +165,15 @@ OData-Version: 4.0
 }
 ```
 
-If `allowedmimetypes` is set, `blockedmimetypes` is ignored. Only the mime types specified in `allowedmimetypes` are allowed.
+If `allowedmimetypes` is set, `blockedmimetypes` is ignored. Only the MIME types specified in `allowedmimetypes` are allowed.
 
-If `blockedmimetypes` isn't empty and `allowedmimetypes` is empty, the following error occurs when someone tries to upload a mime type that is in blocked mime types:
+If `blockedmimetypes` isn't empty and `allowedmimetypes` is empty, the following error occurs when someone tries to upload a MIME type that is in blocked MIME types:
 
 > Name: `MimeTypeBlocked`<br />
 > Code: `0x80072522`<br />
 > Message: `Operation not allowed as mime type image/svg+xml is blocked.`
 
-If `allowedmimetypes` isn't empty, the following error occurs when someone tries to upload a mime type that isn't in `allowedmimetypes`:
+If `allowedmimetypes` isn't empty, the following error occurs when someone tries to upload a MIME type that isn't in `allowedmimetypes`:
 
 > Name: `MimeTypeNotInAllowedList`<br />
 > Code: `0x80072521`<br />

powerapps-docs/developer/data-platform/org-service/samples/azure-aware-custom-plugin.md

@@ -1,7 +1,7 @@
 ---
 title: "Azure aware custom plug-in (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "This sample plug-in can post the pipeline execution context to the Azure Service Bus." # 115-145 characters including spaces. This abstract displays in the search result.
-ms.date: 04/03/2022
+ms.date: 06/19/2023
 author: jaredha
 ms.author: jaredha
 ms.reviewer: jdaly
@@ -20,10 +20,18 @@ The plug-in demonstrates how to obtain the execution context and the tracing ser
 ## How to run this sample
 
 1. Download or clone the [Samples](https://github.com/Microsoft/PowerApps-Samples) repo so that you have a local copy.
-2. Open the sample solution in Visual Studio and sign the assembly with a key.
-3. Register the plug-in using the **Plugin Registration Tool**.
+1. Open the `Azureplugin.sln` solution file located at `PowerApps-Samples\dataverse\orgsvc\C#\Azureplugin` with Visual Studio.
+1. Sign the assembly with a key.
+1. Register the plug-in using the **Plugin Registration Tool**.
 
 > [!NOTE]
 > This sample requires a service endpoint to be created first, and its ID passed to the plug-in constructor through the unsecure configuration parameter when the plug-in step is registered.
 
+More information:
+
+[Write a custom Azure-aware plug-in](../../write-custom-azure-aware-plugin.md)  
+[Register a plug-in](../../register-plug-in.md)
+
+
+
 [!INCLUDE[footer-include](../../../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/write-custom-azure-aware-plugin.md

@@ -1,7 +1,7 @@
 ---
 title: "Write a custom Azure-aware plug-in (Microsoft Dataverse) | Microsoft Docs"
 description: "Learn how to write plug-in code that can post a message or the execution context of the current database transaction to the Azure Service Bus."
-ms.date: 04/03/2022
+ms.date: 06/19/2023
 author: divkamath
 ms.author: dikamath
 ms.reviewer: pehecke
@@ -132,10 +132,11 @@ For a plug-in registered to execute asynchronously, the <xref:Microsoft.Xrm.Sdk.
 
 ### See also
 
-[Azure extensions for Dynamics 365](azure-integration.md)<br />
-[Send Dynamics 365 data over the Microsoft Azure Service Bus](work-data-azure-solution.md)<br />
-[Write a plug-In](write-plug-in.md)<br />
-[Event execution pipeline](event-framework.md)<br />
+[Azure extensions for Dynamics 365](azure-integration.md)  
+[Send Dynamics 365 data over the Microsoft Azure Service Bus](work-data-azure-solution.md)  
+[Sample: Azure aware custom plug-in](org-service/samples/azure-aware-custom-plugin.md)  
+[Write a plug-In](write-plug-in.md)  
+[Event execution pipeline](event-framework.md)  
 [Register and deploy plug-Ins](register-plug-in.md)
 
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/limits-and-config.md

@@ -101,7 +101,7 @@ This list identifies all services to which Power Apps communicates and their usa
 | 127.0.0.1 | http | Power Apps Mobile|
 | ecs.office.com | https | Retrieve feature flags for Power Apps |
 | config.edge.skype.com | https | Retrieve feature flags for Power Apps (backup)|
-| \*.api.powerplatform.com | https | Required for Power Platform API connectivity used internally by Microsoft products, and Power Platform [programmability and extensibility](/power-platform/admin/programmability-extensibility-overview).|
+| api.powerplatform.com<br>\*.api.powerplatform.com | https | Required for Power Platform API connectivity used internally by Microsoft products, and Power Platform [programmability and extensibility](/power-platform/admin/programmability-extensibility-overview).|
 | *.sharepointonline.com| https | Retrieve assets for presenting the header that appears at the top of app playing experiences |
 
 

powerapps-docs/maker/TOC.yml

@@ -104,7 +104,9 @@
       - name: Use timeline
         href: ../user/add-activities.md
       - name: Create and join a Teams meeting from an appointment
-        href: ../user/join-teams-meeting-from-appointments.md  
+        href: ../user/join-teams-meeting-from-appointments.md 
+      - name: Known issues about activities
+        href: ../user/known-issues-activities.md
     - name: Work with email
       items:
       - name: Understand the email experience
@@ -2423,6 +2425,8 @@
           href: ../cards/make-a-card/ui-elements/use-buttons.md
         - name: Add and configure screens
           href: ../cards/make-a-card/screens/use-screens.md
+        - name: Work with repeating controls in cards
+          href: ../cards/make-a-card/ui-elements/data-binding.md
         - name: Control reference
           items: 
             - name: List of controls and properties

powerapps-docs/maker/canvas-apps/connections-list.md

@@ -110,29 +110,33 @@ This type of connection isn't secure because it doesn't rely on end-user authent
 
 In SQL Server, this type of connection is called **SQL Server Authentication**.  Many other database data sources provide a similar capability.  When you publish your application, your users don't need to supply a unique user name and password.  They're using the user name and password you supply when you author the application.  The connection authentication to the data source is **Implicitly Shared** with your users.  Once the application is published, the connection is also published and available to your users.  Your end users can also create applications using any connection using SQL Server authentication that is shared with them.  Your users can't see the user name or password, but the connection will be available to them.  **There are valid scenarios for this type of connection. For instance if you have a read-only database that is available to everyone in the company. Reference data scenarios (for example, a corporate calendar) can be useful for this kind of connection.** More information: [Use Microsoft SQL Server securely with Power Apps](connections/sql-server-security.md)
 
-### Secure Implicit Connections (experimental)
-Power Apps now has support for **[Secure implicit connections (experimental)](working-with-experimental-preview.md)**. The secure implicit shared connections are more secure than the existing implicit connections. Power Apps implicitly shared connections are ones that use a fixed credential such as a SQL Server connection string rather than the end user's specific credentials such as AAD. With this feature, connections are no longer directly shared with the users of Power Apps. Instead, a proxy connection object that only grants access to the underlying resource such as a specific SQL server table is shared. End user authors can't create new applications with either the connection or the proxy connection. This feature also limits the end user to such actions as **get**, **put/patch**, and **delete** that are defined in the corresponding app. The result is that end users who are also authors can't create new applications with either the connection or the proxy connection object.
+### Secure Implicit Connections (preview)
 
-While in preview, an app author must opt-in to use this feature. Eventually, this feature will be on for all apps. With the experimental preview switch turned on for a given Power Apps app, all implicit connections in the app will automatically use this feature.  
+[This section is prerelease documentation and is subject to change.]
 
-#### Enable secure implicit connections for new app
+Power Apps now has full preview support for **[Secure implicit connections](working-with-experimental-preview.md)**. The default setting for this feature is **On**. The secure implicit shared connections are more secure than the existing implicit connections. Power Apps implicitly shared connections are ones that use a fixed credential such as a SQL Server connection string rather than the end user's specific credentials such as AAD. With this feature, connections are no longer directly shared with the users of Power Apps. Instead, a proxy connection object that only grants access to the underlying resource such as a specific SQL server table is shared. End user authors can't create new applications with either the connection or the proxy connection. This feature also limits the end user to such actions as **get**, **put/patch**, and **delete** that are defined in the corresponding app. The result is that end users who are also authors can't create new applications with either the connection or the proxy connection object.
 
-Sign in to [Power Apps](https://make.powerapps.com) and create a new app that uses an implicitly shared connection:
+> [!NOTE]
+> **Secure implicit connections** is now **On** by default for new apps.
+
+#### Notification to update your apps
+If you have applications that may be upgraded to use this feature then you will see a message on the Apps page. It will indicate the number of apps that need your attention.  
+
+   > [!div class="mx-imgBorder"]
+   > ![Notification to update your apps.](./media/connections-list/attention-alert.png)
+
+Select the link and it will open a side panel that will list all of the apps that need attention.  
 
-1. In Power Apps Studio, on the command bar, select **Settings** > **Upcoming features**.
-2. Select the **Experimental** tab.
-3. Set the toggle for **Secure implicit connections** to **On**
    > [!div class="mx-imgBorder"]
-   > ![Secure implicit connections.](./media/connections-list/secure_implicit_connection_option.png)
-3. When you're done, publish the app. 
+   > ![Side panel.](./media/connections-list/app-needs-attention.png)
 
-   To share with different users, see [Sharing](connections-list.md#sharing).
+Select the *open* icon to the right of the app name to open and republish it.  See the directions below.
 
 #### Enable secure implicit connections for an existing app
 
 Open an existing [app open for editing](../../edit-app.md) with implicitly shared connections that has previously been published:
 1. On the command bar, select **Settings** > **Upcoming features**.
-2. From the **Experimental** tab, set the toggle for **Secure implicit connections** to **On**.
+2. From the **Preview** tab, set the toggle for **Secure implicit connections** to **On**.
 3. Save and publish the app.
 
 #### Sharing
@@ -142,7 +146,7 @@ Once the app is published follow these steps to verify that sharing works correc
 - Check if connections are shared with co-owners. If you don't want an end-user to get a connection, then uncheck the **Co-owner** checkbox.
 
    > [!div class="mx-imgBorder"]
-   > ![Co-owner property.](./media/connections-list/co-owner-property.png)
+   > ![Uncheck co-owner.](./media/connections-list/co-owner-property.png)
 
 - To verify the feature works correctly, share the app with a different user who isn't an owner. Once you have shared the app, check the **Connections** list in the **Dataverse** tab in [Power Apps](https://make.powerapps.com) for that user. Verify that the user doesn't have a connection available.
 
@@ -157,7 +161,7 @@ When your app is republished and shared, then end-users won't have access to the
 
 #### Limitations
 
-1. All types of implicitly shared connection work such as action and tabular.
+1. All types of implicitly shared connections work such as action and tabular.
 2. Server and database names are hidden in network traces but visible in the consent dialog. Column names are not hidden.
 3. For tabular connectors, we only limit CRUD actions such as Get, Post, Put, or Delete. If you have permissions to **Put** then you have access to **Post**.
 4. Action based connectors limit based on the specific API being used in the application. 

powerapps-docs/maker/canvas-apps/create-component.md

@@ -52,6 +52,9 @@ Components available inside the app are listed under the **Custom** category in
 
 A component can receive input values and emit data if you create one or more custom properties. These scenarios are advanced and require you to understand [formulas](formula-reference.md) and binding contracts.
 
+> [!NOTE]
+> An experimental feature for enhanced component properties provides even more options for properties, including functions and behavior functions. For more information, see [Canvas component properties (experimental)](./component-properties.md)
+
 **Input property** is how a component receives data to be used in the component. Input properties appear in the **Properties** tab of the right-hand pane if an instance of the component is selected. You can configure input properties with expressions or formulas, just as you configure standard properties in other controls. Other controls have input properties, such as the **Default** property of a **Text input** control.
 
 **Output property** is used to emit data or component state. For example, the **Selected** property on a **Gallery** control is an output property. When you create an output property, you can determine what other controls can refer to the component state.

powerapps-docs/maker/canvas-apps/intro-maker-portal.md

@@ -2,7 +2,7 @@
 title: "Get started with Power Apps| MicrosoftDocs"
 description: How to navigate the Power Apps home page. 
 ms.custom: ""
-ms.date: 11/28/2022
+ms.date: 06/15/2023
 ms.reviewer: "mkaur"
 ms.topic: overview
 author: "mkaur"
@@ -134,6 +134,8 @@ For best results, start by ensuring that the home page is set to the right envir
 > [!div class="mx-imgBorder"]
 > ![Environment switcher.](media/intro-maker-portal/environment-switcher.png)
 
+Environments can be managed using [Power Platform admin center](/power-platform/admin/environments-overview#manage-environments-in-the-power-platform-admin-center).
+
 ### Notifications
 
 Select the bell icon to see notifications. Notifications are stored in the notification center until you dismiss them or when they expire.