Merge branch 'main' into jdaly-main-discovery-unification

Author: JimDaly

powerapps-docs/developer/component-framework/reference/mode/trackcontainerresize.md

@@ -42,7 +42,7 @@ The following table shows the strategies that you can use to control the height
 | Canvas apps       | `dataset` & `field`                    | `height: allocatedWidth`                                     | `width: allocatedHeight` |
 | Canvas apps       | `dataset` & `field` (full screen mode) | `height: "100%"`                                             | `width: "100%"`          |
 
-If the  of `allocatedWidth` and `allocatedHeight` change after the first `updateView` is called, then a subsequent `updateView` is called with "layout" added to the `context.updatedProperties`. More information: [UpdatedProperties](..\updatedproperties.md).
+If the values of `allocatedWidth` and `allocatedHeight` change after the first `updateView` is called, then a subsequent `updateView` is called with "layout" added to the `context.updatedProperties`. More information: [UpdatedProperties](..\updatedproperties.md).
 
 ## Available for 
 

powerapps-docs/developer/data-platform/TOC.yml

@@ -407,6 +407,8 @@
       href: isv-app-usage-analytics.md
     - name: Install failures analytics
       href: isv-install-failure-analytics.md
+    - name: Auto App Updates (Preview) 
+      href: isv-app-management-autoupdate.md
 - name: Create applications
   href: connect-dataverse.md
   items:

powerapps-docs/developer/data-platform/application-insights-ilogger.md

@@ -1,7 +1,7 @@
 ---
-title: "Write Telemetry to your Application Insights resource using ILogger (preview)(Microsoft Dataverse) | Microsoft Docs"
+title: "Write Telemetry to your Application Insights resource using ILogger (Microsoft Dataverse) | Microsoft Docs"
 description: "When you enable Application Insights for your organization, any plug-ins written using the ILogger Interface provided in the SDK will write telemetry to your Application Insights resource."
-ms.date: 04/03/2022
+ms.date: 07/14/2022
 author: divka78
 ms.author: dikamath
 manager: sunilg
@@ -18,12 +18,10 @@ contributors:
  - phecke
 ---
 
-# Write Telemetry to your Application Insights resource using ILogger (Preview)
-
-[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
+# Write Telemetry to your Application Insights resource using ILogger
 
 > [!IMPORTANT]
-> To use this capability you must first enable the Application Insights integration preview feature. More information: [Preview: Analyze model-driven apps and Microsoft Dataverse telemetry with Application Insights](/power-platform/admin/analyze-telemetry)<p/>
+> To use this capability you must first enable the Application Insights integration feature. More information: [Analyze model-driven apps and Microsoft Dataverse telemetry with Application Insights](/power-platform/admin/analyze-telemetry)<p/>
 > There is presently no support of `ILogger` within a plug-in profiling/debug session of the Plug-in Registration tool or the Power Platform Tools extension for Visual Studio.
 
 When you enable Application Insights for your organization, any plug-ins written using the [ILogger Interface](/dotnet/api/microsoft.xrm.sdk.plugintelemetry.ilogger) provided in the Organization Service SDK assemblies will write telemetry to your Application Insights resource.
@@ -354,4 +352,4 @@ The formatted message text is captured as part of the `customDimensions`.
 [PluginTraceLog Table](reference/entities/plugintracelog.md)
 
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/configure-entity-relationship-cascading-behavior.md

@@ -109,7 +109,7 @@ The `CascadeConfiguration` (<xref:Microsoft.Xrm.Sdk.Metadata.CascadeConfiguratio
 ### About the assign action
 The assign action allows the owner, the Owning Business Unit or both owner and business unit updates to be cascaded down to all child records when the parent record is updated.
 
-#### Allowed record ownership across business unites not enabled
+#### Allowed record ownership across business units not enabled
 When the [allow record ownership across business units](/power-platform/admin/wp-security-cds#to-enable-this-matrix-data-access-structure-preview) is not enabled, the Owning Business Unit column can't be explicitly updated when changing the record’s owner. The following lists the cascading behaviors when the parent’s record owner is updated.
 
 If you update the owner:
@@ -125,7 +125,7 @@ If you update the owner:
   - Child records’ owner is not updated (no cascade)
   - Child records’ business unit is not updated (no cascade)
 
-#### Allowed record ownership across business unites is enabled
+#### Allowed record ownership across business units is enabled
 When [allow record ownership across business units](/power-platform/admin/wp-security-cds#to-enable-this-matrix-data-access-structure-preview) is enabled,
 the Owning Business Unit column can be explicitly updated when changing the record’s owner. The following lists the cascading behaviors when the parent’s record owner and/or the business unit is updated.
 

powerapps-docs/developer/data-platform/dataverse-odata-dataflows-migration.md

@@ -46,7 +46,8 @@ In this article, we walk you through how to migrate data between Dataverse envir
 
 1. When importing relationships, multiple dataflows are required.
 
-    Tables that are one (parent/independent) to many (children/dependent) require separate dataflows. Configure the parent dataflow to run before any child tables, since the data in the parent needs to be loaded first to correctly map to the columns in the corresponding child tables.
+    Tables that are one (parent/independent) to many (children/dependent) require separate dataflows. Configure the parent dataflow to run before any child tables, since the data in the parent needs to be loaded first to correctly map to the columns in the corresponding child tables. 
+    Additionally, you must create an [alternate key](/powerapps/maker/data-platform/define-alternate-keys-reference-records?WT.mc_id=DX-MVP-5003800) in the parent table before being given the option to set a lookup column on the child table. Without a key defined on a parent table, you will be unable to populate lookup columns on any child tables.   
 
 ## Step 2: Get the OData endpoint 
 
@@ -96,7 +97,6 @@ In the **target** environment, create a new dataflow with the OData connector.
     > [!div class="mx-imgBorder"]
     > ![Confirm the column values are correct.](./media/enter-odata-connector-parameters.png "Confirm the column values are correct")
 
-
     | Column                   | Description                                                                                                                          |
     |--------------------------|--------------------------------------------------------------------------------------------------------------------------------------|
     | URL                      | Provide the Service Root URL in the URL column of the connection settings.                                                           |
@@ -148,13 +148,11 @@ For each table chosen, select the behavior for importing that table in these set
 - **Load to existing table (recommended)**
 
     - The dataflow syncs data from the source environment's table to the target environment, and the same table schema is already defined in the target environment.
-
-    - Ideally, use the same solution in both target and source environments to make data transfer seamless. Another advantage to having a predefined tables is more control over which solution the tables is defined in and the prefix.
-    
-    - Choose **Delete rows that no longer exist in the query output**. This ensures that the relationships will map correctly because it maintains the values for the lookups.
-    
+    - Ideally, use the same solution in both target and source environments to make data transfer seamless. Another advantage to having a predefined table is more control over which solution the table is defined in and the prefix.    
+    - Choose **Delete rows that no longer exist in the query output**. This ensures that the relationships will map correctly because it maintains the values for the lookups. To use this feature, you must first define an [alternate key](https://docs.microsoft.com/en-us/powerapps/maker/data-platform/define-alternate-keys-reference-records?WT.mc_id=DX-MVP-5003800) on the target/existing table so the dataflow can determine whether to update existing records or create new ones.
+      > [!NOTE]
+      > This option should only be used if the goal is to make data in source and target the same. If another process in the destination environment adds data to the same table (or if there is other existing data in the table) it will be deleted by this dataflow.
     - If the schema is identical in both source and target tables, you can select **Auto map** to quickly map the columns.
-
     - Requires a key configuration in the target environment (as the unique identifier columns are not available to modify).
 
   > [!IMPORTANT]
@@ -163,7 +161,6 @@ For each table chosen, select the behavior for importing that table in these set
 - **Load to new table (not recommended)**
 
     - Ideally there should be a table predefined in the target environment from the same solution import as the source environment. However, there are cases where this might not be feasible, so this is an option if there is no existing table to load to. 
-
     - It creates a new custom table in the target environment's default solution.
 
 - There is an option to **Do not load**, but do not include tables in the dataflow that are not being loaded. You can select **Back** from this menu to return to the Power Query menu and remove the tables that are not needed.

powerapps-docs/developer/data-platform/dataverse-sql-query.md

@@ -2,7 +2,7 @@
 title: "Use SQL to query data (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn how to query Microsoft Dataverse table data using SQL." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 03/12/2021
+ms.date: 07/08/2022
 ms.reviewer: "pehecke"
 
 ms.topic: "article"
@@ -99,6 +99,10 @@ Dataverse choice columns are represented as \<choice\>Name and \<choice\>Label i
 >[!TIP]
 > After making changes to labels for a choice column, the table needs to have customizations published. 
 
+### Reported SQL version
+The Dataverse TDS endpoint emulates Microsoft SQL Server read-only query capabilities over the Dataverse business logic. Dataverse returns the current SQL Azure version 12.0.2000.8 for `select @@version`.
+
+
 ## Limitations
 
 There is an 80-MB maximum size limit for query results returned from the Dataverse endpoint. Consider using data integration tools such as [Azure Synapse Link for Dataverse](../../maker/data-platform/export-to-data-lake.md) and [dataflows](/power-bi/transform-model/dataflows/dataflows-introduction-self-service) for large data queries that return over 80 MB of data. More information: [Importing and exporting data](../../maker/data-platform/import-export-data.md)

powerapps-docs/developer/data-platform/email-activity-entities.md

@@ -22,7 +22,7 @@ contributors:
 
 [!INCLUDE[cc-terminology](includes/cc-terminology.md)]
 
-The email activity lets you track and manage email communications with customers. Microsoft Dataverse includes the Email Router software that manages the routing of email to or from Dataverse. The email activity is delivered using email protocols. Email Router supports the following email protocols: Exchange Web services, POP3, and SMTP. In addition to the Email Router software, the email activity can also be delivered by using Dynamics 365 for Outlook.  
+The email activity lets you track and manage email communications with customers. 
 
 <a name="Actions"></a>   
 
@@ -121,4 +121,4 @@ ObjectId = new EntityReference(Template.EntityLogicalName, _templateId), ObjectT
  [ActivityMimeAttachment table](/reference/entities/activitymimeattachment.md)
 
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/isv-app-management-autoupdate.md

@@ -0,0 +1,82 @@
+---
+title: Auto App Updates (Preview) | Microsoft Docs
+description: Learn about the latest auto update feature for apps.
+ms.date: 06/30/2022
+author: angela21k
+ms.author: angelakim
+ms.reviewer: jdaly
+suite: powerapps
+ms.topic: article
+ms.subservice: dataverse-developer
+search.audienceType: 
+  - developer
+search.app: 
+  - PowerApps
+contributors: 
+  - JimDaly
+---
+
+# Auto App Updates (Preview)
+
+[!INCLUDE [cc-preview-features-definition](../../includes/cc-preview-features-definition.md)]
+
+App Auto Update is a new feature in public preview that allows automatic updates of applications installed through AppSource. This feature helps both publishers and customers keep software up to date in a simple and controlled way with minimal administrative overhead.  
+
+Automatic updates in the preview will be limited to:  
+
+- **Explicit tenant admin opt-in**: Tenant admin user must opt-in from the Power Platform Admin center to enable the feature. 
+
+- **Pre-approved publishers**: Tenant admin user must indicate which publishers are permitted to automatically update apps in their environment once opted-in from the Power Platform Admin center.
+
+- **Dark hours only**: To further minimize impact, automatic updates will only happen during dark hours defined by either the customer or at geo level.  
+
+## Enabling Auto App Update  
+
+> [!NOTE]
+> Publishers do not require additional action to enable automatic updates for their apps. Only tenant admin users are required to act if they want to opt-in to this feature for select publishers.
+
+1. Log into the Power Platform Admin center as an admin user. From the Environments page, select an environment and click on **Settings**.
+
+   :::image type="content" source="media/auto-app-update-0.jpg" alt-text="Power Platform Admin Center Environment":::
+
+1. From the environment settings page, under the **Updates** section, click to open the **App Update Settings** page.  
+
+   :::image type="content" source="media/auto-app-update-1.jpg" alt-text="Power Platform Admin Center Environment Settings":::
+
+1. Toggle the configurator to **'On'** to opt-in to the feature.  From the drop-down list of publishers, select for which publishers you want to automatically update apps.
+
+   :::image type="content" source="media/auto-app-update-2.jpg" alt-text="Configure App Update Settings":::
+
+1. Click **Save** to keep your changes.
+
+
+## Monitoring Opt-in Environments in ISV Studio 
+
+As a publisher with access to ISV Studio, you can view details about your automatic updates and opt-in rates.
+ 
+1. Login to ISV Studio. From the navigation menu, click on **Analytics** and **Published apps.**
+Graphical user interface, application
+
+   :::image type="content" source="media/auto-app-update-3.jpg" alt-text="ISV Studio Published Apps":::
+ 
+1. Select a specific app and click the **Auto Updates** tab to view opt-in rates for publishers and environments, which organizations have opted out, as well as a detailed list of version history.
+
+   :::image type="content" source="media/auto-app-update-4.png" alt-text="ISV Studio Auto Updates":::
+
+1. From the Version Update History table, click **View Details** to view details about the deployment status by region.
+
+   :::image type="content" source="media/auto-app-update-5.jpg" alt-text="ISV Studio Version Update Details":::
+
+> [!NOTE]
+> The Cancel Deployment button will cancel automatic updates for any regions with release status in progress or to be scheduled.
+
+### See also
+
+[Introduction to ISV Studio for the Power Platform](isv-app-management.md)  
+[Home page](isv-app-management-homepage.md)<br/> 
+[App page](isv-app-management-apppage.md)<br/> 
+[AppSource checker](isv-app-management-appsource-checker.md)<br/> 
+[Connector Certification](isv-app-management-certification.md)
+
+
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]