Live publish

Author: buck1ey

powerapps-docs/developer/data-platform/dependent-assembly-plugins.md

@@ -1,13 +1,12 @@
 ---
 title: "Dependent Assembly plug-ins (preview) (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn how to include additional assemblies that your plug-in assembly can depend on." # 115-145 characters including spaces. This abstract displays in the search result.
-ms.date: 12/01/2022
+ms.date: 01/05/2023
 ms.reviewer: jdaly
 ms.topic: article
 author: divkamath # GitHub ID
 ms.subservice: dataverse-developer
 ms.author: dikamath # MSFT alias of Microsoft employees only
-manager: sunilg # MSFT alias of manager or PM counterpart
 search.audienceType: 
   - developer
 search.app: 
@@ -307,10 +306,6 @@ More information:
 
 The following are known issues that should be resolved before dependent assemblies for plug-ins becomes generally available.
 
-### Asynchronous plug-in steps do not work
-
-If you use dependent assemblies for a plug-in registered for an asynchronous step an error with the message `Expected non-empty Guid.` will occur.
-
 ### Plug-in profiler
 
 You cannot use Plug-in Profiler to debug plug-ins that are part of a plug-in package. More information: [Use Plug-in profiler](debug-plug-in.md#use-plug-in-profiler)
@@ -329,6 +324,9 @@ You can manually edit this for each security role following the steps here: [Edi
 
 :::image type="content" source="media/set-pluginpackage-read-access.png" alt-text="Setting plugin package read access.":::
 
+### Custom API cannot use dependent assembly plug-ins
+
+The custom API will not work after being imported as part of a solution.
 
 ### See also
 

powerapps-docs/developer/data-platform/troubleshoot-plug-in.md

@@ -18,7 +18,6 @@ contributors:
 
 [!INCLUDE[cc-terminology](../../includes/cc-terminology.md)]
 
-
 This .NET 6.0 sample demonstrates how to perform parallel data operations using the Dataverse Web API.
 
 This sample uses the common helper code in the [WebAPIService class library (C#)](webapiservice.md).
@@ -62,7 +61,7 @@ To encounter service protection limits with this sample you should raise the `nu
 
 This example uses the [Parallel.ForEachAsync Method](/dotnet/api/system.threading.tasks.parallel.foreachasync) introduced with .NET 6.0.
 
-This sample processes a list of requests to create account records, sending the requests in parallel and then uses the data returned to add requests to delete the created accounts to a [ConcurrentBag](/dotnet/api/system.collections.concurrent.concurrentbag-1?view=net-6.0). After the records are created, the number of seconds to create the records is displayed.
+This sample processes a list of requests to create account records, sending the requests in parallel and then uses the data returned to add requests to delete the created accounts to a [ConcurrentBag](/dotnet/api/system.collections.concurrent.concurrentbag-1?view=net-6.0&preserve-view=true). After the records are created, the number of seconds to create the records is displayed.
 
 Then, the delete requests in the `ConcurrentBag` are processed and the time spent deleting the records is displayed.
 

powerapps-docs/developer/data-platform/webapi/samples/webapiservice-parallel-operations.md

@@ -2,7 +2,7 @@
 title: "Create an Azure Synapse Link for Dataverse with your Azure Synapse Workspace | MicrosoftDocs"
 description: "Learn how to export table data to Azure Synapse Analytics in Power Apps"
 ms.custom: ""
-ms.date: 09/30/2022
+ms.date: 01/05/2023
 ms.reviewer: "Mattp123"
 ms.suite: ""
 ms.tgt_pltfrm: ""
@@ -39,7 +39,7 @@ You can use the Azure Synapse Link to connect your Microsoft Dataverse data to A
 
 ## Prerequisites
 
-- Azure Data Lake Storage Gen2: You must have an Azure Data Lake Storage Gen2 account and **Owner** and **Storage Blob Data Contributor** role access. Your storage account must enable **Hierarchical namespace** and it is recommended that replication is set to **read-access geo-redundant storage (RA-GRS)**. 
+- Azure Data Lake Storage Gen2: You must have an Azure Data Lake Storage Gen2 account and **Owner** and **Storage Blob Data Contributor** role access. Your storage account must enable **Hierarchical namespace** and **public network access** for both initial setup and delta sync. **Allow storage account key access** is required only for the initial setup. We recommend that replication is set to **read-access geo-redundant storage (RA-GRS)**.  
 
 - Synapse workspace: You must have a Synapse workspace and the **Synapse Administrator** role access within the Synapse Studio. The Synapse workspace must be in the same region as your Azure Data Lake Storage Gen2 account with **public network access** enabled. The storage account must be added as a linked service within the Synapse Studio. To create a Synapse workspace, go to [Creating a Synapse workspace](/azure/synapse-analytics/get-started-create-workspace).
 
@@ -76,7 +76,7 @@ You can use the Azure Synapse Link to connect your Microsoft Dataverse data to A
 You can follow the steps above to create a link from one environment to multiple Azure Synapse Analytics workspaces and Azure data lakes in your Azure subscription by adding an Azure data lake as a linked service on a Synapse workspace. Similarly, you could create a link from multiple environments to the same Azure Synapse Analytics workspace and Azure data lake, all within the same tenant.
 
 > [!NOTE]
-> The data exported by Azure Synapse Link service is encrypted at rest in Azure Data Lake Storage Gen2. Additionally, transient data in the blob storage is also encrypted at rest. Encryption in Azure Data Lake Storage Gen2 helps you protect your data, implement enterprise security policies, and meet regulatory compliance requirements. More information: [Azure Data Encryption-at-Rest]( /azure/security/fundamentals/encryption-atrest)
+> The data exported by Azure Synapse Link service is encrypted at transit using Transport Layer Security(TLS) 1.2 or higher and encrypted at rest in Azure Data Lake Storage Gen2. Additionally, transient data in the blob storage is also encrypted at rest. Encryption in Azure Data Lake Storage Gen2 helps you protect your data, implement enterprise security policies, and meet regulatory compliance requirements. More information: [Azure Data Encryption-at-Rest]( /azure/security/fundamentals/encryption-atrest)
 >
 > Currently, you can't provide public IPs for the Azure Synapse Link for Dataverse service that can be used in **Azure Data Lake firewall settings**. Public IP network rules have no effect on requests originating from the same Azure region as the storage account. Services deployed in the same region as the storage account use private Azure IP addresses for communication. Thus, you can't restrict access to specific Azure services based on their public outbound IP address range.
 More information: [Configure Azure Storage firewalls and virtual networks]( /azure/storage/common/storage-network-security)

powerapps-docs/developer/data-platform/webapi/samples/webapiservice.md

@@ -4,7 +4,7 @@ metadata:
   description: Get answers to frequently asked questions about Power Apps Azure Synapse Link for Dataverse.
   author: sabinn-msft
   ms.search.keywords: 
-  ms.date: 12/15/2022
+  ms.date: 01/05/2023
   ms.author: sabinn
   ms.reviewer: 
   contributors: JasonHQX
@@ -34,6 +34,9 @@ sections:
         Deleting a row is handled differently based on which data write options you choose:
         - In-place update: This is the default mode and when you delete a table row in this mode, the row is also deleted from the corresponding data partition in the Azure Data Lake. In other words, data is hard deleted from the destination. 
         - Append-only: In this mode, when a Dataverse table row is deleted, it is not hard deleted from the destination. Instead, a row is added and set as isDeleted=True to the file in the corresponding data partition in Azure Data Lake.
+   - question:  Why does the Model.json file increase or change in length for the data types and doesn't keep what is defined in Dataverse?
+     answer: |
+        Model.json keeps the database length for the column's size. Dataverse has a concept of database length for each column. If you create a column with a size of 200 and later reduce it to 100, Dataverse still allows your existing data to be present in Dataverse. It does that by keeping DBLength to 200 and MaxLength to 100. What you see in Model.json is DBLength and if you use that for downstream processes you will never provision lesser space for your Dataverse columns.
    - question: What date and time formats can be expected in exported Dataverse tables?
      answer: |
         There are three date and time formats that can be expected in the exported Dataverse tables.
@@ -49,18 +52,30 @@ sections:
    - question: When should I use a yearly or monthly partition strategy?
      answer: |
         For Dataverse tables where data volume is high within a year, we recommend you use monthly partitions. Doing so results in smaller files and better performance. Additionally, if the rows in Dataverse tables are updated frequently, splitting into multiple smaller files help improve performance in the case of in-place update scenarios.
-   - question: When do I use Append only mode for a historical view of changes?
+   - question: What is append only mode and what is the difference between append only and in-place update mode?
+     answer: |
+        In append only mode, incremental data from Dataverse tables are appended to the corresponding file partition in the lake. For more information: [Advanced Configuration Options in Azure Synapse Link](azure-synapse-link-advanced-configuration.md)
+   - question: When do I use append only mode for a historical view of changes?
      answer: |
          Append only mode is the recommended option for writing Dataverse table data to the lake, especially when the data volumes are high within a partition with frequently changing data. Again, this is a commonly used and highly recommended option for enterprise customers. Additionally, you can choose to use this mode for scenarios where the intent is to incrementally review changes from Dataverse and process the changes for ETL, AI, and ML scenarios. Append only mode provides a history of changes, instead of the latest change or in place update, and enables several time series from AI scenarios, such as prediction or forecasting analytics based on historical values. 
+   - question: How do I retrieve the most up-to-date row of each record and exclude deleted rows when I export data in append only mode?
+     answer: |
+        In append only mode, you should identify the latest version of record with the same ID using **VersionNumber** and **SinkModifiedOn** then apply **isDeleted=0** on the latest version.
+   - question: Why do I see duplicated version numbers when I export data using append only mode?   
+     answer: |
+         For append only mode, if Azure Synapse Link for Dataverse does not get an acknowledgement from the Azure data lake that the data has been committed due to any reason such as network delays, Synapse Link will retry in those scenarios and commit the data again. The downstream consumption should be made resilient to this scenario by filtering data using SinkModifiedOn.     
    - question: Which Dataverse tables are not supported for export?
      answer: |
         Any table that does not have change tracking enabled will not be supported in addition to following system tables:
         - Attachment
         - String Map
         - Calendar
-   - question: Which Dataverse tables use Append only by default?
+   - question: Does Azure Synapse Link support calculated columns?
+     answer: |
+        Yes. In Dataverse, the calculated column keeps only the formula information and the real value depends on the base entity column so the calculated column will be updated if and only if all data (base tables) related to calculated columns are exported via Azure Synapse Link.
+   - question: Which Dataverse tables use append only mode by default?
      answer: |
-        All tables that do not have a createdOn field will be synced using Append only mode by default. This includes relationship tables as well as the ActivityParty table.
+        All tables that do not have a createdOn field will be synced using append only mode by default. This includes relationship tables as well as the ActivityParty table.
    - question: Why does Azure Synapse Link for Dataverse require all resources to be in the same region and what can I do about it?
      answer: |
         To ensure high performance and low latency in addition to preventing egress charges, Synapse Link requires all resources to be located in the same region. If you have a cross-region scenario, you can:

powerapps-docs/developer/data-platform/workflow/workflow-extensions.md

@@ -45,7 +45,7 @@ In this step, you'll create a new basic form in portals and then add the control
 
 ### Step 3.1. Create a new basic form
 
-1. Open the [Portal Management app](../configure/configure-portal.md).
+1. Open the [Portal Management app](configure/configure-portal.md).
 
 1. On the left pane under **Content**, select **Basic Forms**.
 
@@ -65,7 +65,7 @@ In this step, you'll create a new basic form in portals and then add the control
 
 ### Step 3.2. Add the rich text editor control to the basic form
 
-1. Open the [Portal Management app](../configure/configure-portal.md).
+1. Open the [Portal Management app](configure/configure-portal.md).
 
 1. On the left pane under **Content**, select **Basic Forms**.
 
@@ -153,7 +153,7 @@ For using and storing images in the rich text editor on the portal, you'll need
     > [!TIP]
     > If you don't see the form, select **Sync Configuration** to synchronize changes from Dataverse.
 
-1. Under **Permissions**, select **Manage table permissions** and make sure that you have the appropriate [table permissions](../configure/assign-entity-permissions.md) and [web roles](../configure/create-web-roles.md) configured for the Dataverse table associated to the form.
+1. Under **Permissions**, select **Manage table permissions** and make sure that you have the appropriate [table permissions](configure/assign-entity-permissions.md) and [web roles](configure/create-web-roles.md) configured for the Dataverse table associated to the form.
 
     > [!NOTE]
     > By default, the **feedback** table has **create** permissions configured for the default web roles. For more information, go to [Contact us sample](contact-us-sample.md).