Merge pull request #10272 from MicrosoftDocs/milindav-jul-3-updates

Milindav jul 3 updates

Author: Mattp123

powerapps-docs/maker/data-platform/azure-synapse-link-select-FnO-data.md

@@ -1,7 +1,7 @@
 ---
 title: Choose finance and operations data in Azure Synapse Link for Dataverse
 description: Learn how to choose Dynamics 365 finance and operations apps data in Microsoft Azure Synapse Link for Dataverse and work with Azure Synapse Link and Power BI.
-ms.date: 06/18/2024
+ms.date: 07/02/2024
 ms.reviewer: matp 
 ms.topic: "how-to"
 applies_to: 
@@ -327,9 +327,9 @@ You'll also notice additional metadata fields appended by the system for each da
 | `SinkCreatedOn` | Indicates the date the record was written to the data lake. <br>In case of CSV change data (incremental update), data and time data was written to lake is shown. For table data in Delta format, indicates the date and time of Delta Lake conversion.  | You can use this date similar to the data lake modified date time field in the export to data lake feature. |
 | `SinkModifiedOn` | Indicates the date the record was modified. In case of tables in Delta format files as well as incremental CSV files, contains the same date time as `SinkCreatedOn`. | You can use this date similar to the data lake modified date time field in export to data lake feature. |
 | `sysdatastatecode` | If 1, this record is archived using the long term data retention feature. If 0 this is a live record. | You can use this field to identify finance and operations records that have been archived (and deleted from live data). The same field is available for for CSV change data (incremental update). |
-| `sysrowversion` | Used internally to determine incremental or delta changed to be processed. | Because `sysrowversion` is used internally, don't use this field. |
+| `sysrowversion` | Version number maintained in each finance and operations apps record that determines whether changes have been made to data. This field is used by the system to determine incremental or delta changes to process. | `sysrowversion` is used internally, you can use this field as a *watermark* to determine the last version of record that was updated. This field might be empty for Dynamics 365 customer engagement apps tables. |
 | `tableid` |  Contains a unique ID of each table | Contains the table ID from finance and operations. |
-| `versionnumber` | Used internally - contains the last version of the row that has been synced to data lake. | Because `versionnumber` is used internally, don't use this field.  |
+| `versionnumber` | Used internally - contains the last version of the row that has been synced to the data lake. | Similar to the `sysrowversion` this field contains the last processed version for Dynamics customer engagement apps tables. In case of Dynamics finance and operations apps tables, this field contains the same value as `sysrowversion`. |
 
 ## Reacting to system events and generating audit reports
 

powerapps-docs/maker/data-platform/azure-synapse-link-transition-from-FnO.md

@@ -1,7 +1,7 @@
 ---
 title: Transition from legacy data integration services to Fabric link and Azure Synapse Link for Dataverse
 description: Learn how to transition from Export to Data Lake, BYOD, and data export service to link to Microsoft Fabric and Azure Synapse Link for Microsoft Dataverse.
-ms.date: 05/30/2024
+ms.date: 07/02/2024
 ms.reviewer: matp 
 ms.topic: "how-to"
 applies_to: 
@@ -15,7 +15,7 @@ ms.custom: bap-template
 ---
 # Transition from legacy data integration services
 
-Data export service, [bring your own database (BYOD)](/dynamics365/fin-ops-core/dev-itpro/analytics/export-entities-to-your-own-database), and [Export to Data Lake](/dynamics365/fin-ops-core/dev-itpro/data-entities/azure-data-lake-ga-version-overview) were features introduced in Dynamics 365 apps to export data for analytics and data integration scenarios. These services enabled IT admins and specialists to export data into external databases or data lakes and build data integration pipelines. While we improved these services over the years with updates as part of unification of Dynamics 365 with the power platform, we rearchitected the same capabilities of these disparate services into simpler, unified experiences built into Power Apps (make.powerapps.com). With a transition to Microsoft Fabric link or upgrade to Azure Synapse Link, the re-architected services provide you with an easy ramp to benefit from AI and Copilot investments in Microsoft Dataverse and Fabric.
+Data export service, [bring your own database (BYOD)](/dynamics365/fin-ops-core/dev-itpro/analytics/export-entities-to-your-own-database), and [Export to Data Lake](/dynamics365/fin-ops-core/dev-itpro/data-entities/azure-data-lake-ga-version-overview) were features introduced in Dynamics 365 apps to export data for analytics and data integration scenarios. These services enabled IT admins and specialists to export data into external databases or data lakes and build data integration pipelines. While we improved these services over the years with updates as part of unification of Dynamics 365 with the power platform, we rearchitected the same capabilities of these disparate services into simpler, unified experiences built into Power Apps (make.powerapps.com). With a transition to Microsoft Fabric link or upgrade to Azure Synapse Link, the rearchitected services provide you with an easy ramp to benefit from AI and Copilot investments in Microsoft Dataverse and Fabric.
 
 If you're a customer using any of the previous generation services, this article provides guidance on upgrading to the new experiences, benefiting from innovations, as well as reducing end-to-end expenses and effort.
 
@@ -189,15 +189,15 @@ Currently, there are several limitations that are being addressed by the product
 
 |Known issue |Fixes and Workarounds |
 |---------|---------|
-|When adding a large number of tables at once, the system makes an initial copy of data. <br> There are rare cases, especially in smaller environments and Tier-2 sandboxes, where operational workloads can slow down and initialize time might become much longer. | This might impact smaller environments with fewer Application Object Server (AOS) servers (compute resources). </p><p>In Azure Synapse Link, add five tables at a time if your environment is a Tier-2 sandbox. Once the initialization completes, you can add more. <br><br> Fabric link feature scales initialization workloads up and down as available compute resources at roughly two concurrent tables per AOS. <br> For example, if you have five AOS servers in your environment, the system concurrently initializes up to 10 tables.</p><p> <br><br> Update your finance and operations environment to either: <br> - PU 63 cumulative update 7.0.7198.95 <br> -PU 62 cumulative update 7.0.7120.155. <br> This update redacts `varBinary` fields and `varBinary` attachments from tables added to Azure Synapse Link and Fabric link, which reduces impact to operational workloads. |
+|When adding a large number of tables at once, the system makes an initial copy of data. <br> There are rare cases, especially in smaller environments and Tier-2 sandboxes, where operational workloads can slow down and initialize time might become much longer. | This might impact smaller environments with fewer Application Object Server (AOS) servers (compute resources). </p><p>In Azure Synapse Link and Fabric Link you can add multiple tables at once by pasting a comma separated list of tables. System scales initialization workloads up and down as available compute resources at roughly two concurrent tables per AOS. <br> For example, if you have five AOS servers in your environment, the system concurrently initializes up to 10 tables.</p><p> <br><br> Update your finance and operations environment to either: <br> - PU 63 cumulative update 7.0.7198.95 <br> -PU 62 cumulative update 7.0.7120.155. <br> This update redacts `varBinary` fields and `varBinary` attachments from tables added to Azure Synapse Link and Fabric link, which reduces impact to operational workloads. |
 | When adding tables, the system makes an initial copy of data. In some cases, especially with very large tables, initialization might take longer or appear stuck for several days | Update the finance and operation apps environment to either: <br>- PU 63 cumulative update 7.0.7198.91 <br>-PU 62 cumulative update 7.0.7120.152 <br> This update enables faster initialization of large tables (more than 200M rows). <br><br> We enabled indexes to enable faster data sync. In case there’s an ongoing transaction in the operational database, index creation needs to wait for completion of the transaction. The prolonged wait, sometimes due to dormant transactions, might delay the initialization process. In such cases, system administrator can detect and force index creation. |
 | In case your Dataverse environment is located in an Azure region different than the one where your Fabric capacity is located, you can’t use the **Link to Fabric** feature. | As of April 30, 2024, you can link to a Fabric capacity located within the same geographic boundary, such as United States. <br><br> Notice that you might incur networking charges in Fabric due to data transfer between Azure regions. |
 | In case your Dataverse environment is located in an Azure region different than the one where your data lake or Synapse workspace is located, you can’t use the Azure Synapse Link feature. | As of April 30, 2024, you can link to a storage account located within the same geographic boundary, such as United States. <br><br> Notice that you might incur networking charges in Azure resources like data lakes if they aren't located within the same Azure region. |
 | AOS authorization is a way to secure sensitive data fields in finance and operation apps against data exfiltration scenarios. <br> If the table selected contains data columns that are secured via AOS authorization, those columns are ignored and the exported data doesn't contain the column. <br><br> For example, a custom table column *TaxLicenseNum* has the metadata property `AOS Authorization` set to **Yes**. This column is ignored | Update your finance and operations environment to these versions or later: <br>- PU 63:7.0.7198.105 <br>- PU 62:7.0.7120.159 <br>With this update, AOS authorization fields are added to tables. <br>- Incremental updates include this column. <br> -	Modified records show these columns and value. <br> -	Full refresh includes these fields and all values. |
 | If the table selected contains data columns that are of **Array** type, those columns are ignored and the exported data doesn't contain the column. <br><br>For example, in a custom table named *WHSInventTable*, columns `FilterCode` and `FilterGroup` are of type array. These columns aren't exported with Azure Synapse Link. | There's no workaround to this issue. We're working to enable this feature in a future update. <br><br> Join [Viva engage group](https://aka.ms/synapselinkfordynamics) to stay in touch and onboard preview features when available. |
-| In case of finance and operations apps tables that exhibit [valid time stamp behavior](/dynamicsax-2012/developer/valid-time-state-tables-and-date-effective-data), only the data rows that are currently valid are exported with Azure Synapse Link. <br><br> For example, the `ExchangeRate` table contains both current and previous exchange rates. Only currently valid exchange rates are exported in Azure Synapse Link. | As a workaround, until this issue is fixed, use a table such as **ExchangeRateBIEntity**. <br>Join [Viva engage group](https://aka.ms/synapselinkfordynamics) to stay in touch and onboard preview features. |
+| In case of finance and operations apps tables that exhibit [valid time stamp behavior](/dynamicsax-2012/developer/valid-time-state-tables-and-date-effective-data), only the data rows that are currently valid are exported with Azure Synapse Link. <br><br> For example, the `ExchangeRate` table contains both current and previous exchange rates. Only currently valid exchange rates are exported in Azure Synapse Link. | Update your finance and operations environment to <br> - Version 10.0.38 (PU62) platform update 7.0.7279.58  <br> -  Version 10.0.39 (PU63) platform update 7.0.7198.143 <br> - Version 10.0.40 (PU64) platform update 7.0.7120.179 <br><br> With this update, expired data rows are added to tables. You need to perform a full refresh to include previous rows. |
 |[Table inheritance and derived tables](/dynamicsax-2012/developer/table-inheritance-overview) are concepts in finance and operations apps. When choosing a derived table from finance and operations apps, columns from the corresponding base table currently aren't included. | You need to select the base table in addition to the derived table if you need access to these columns. <br> You can use [this FastTrack solution provided via GitHub](https://github.com/microsoft/Dynamics-365-FastTrack-Implementation-Assets/tree/master/Analytics/DataverseLink/DataIntegration#derived-tables). This solution creates views, which include columns from base tables. |
-| Export more than 1,000 tables via Azure Synapse Link or add more than 1,000 tables to Fabric link. |  If you're using Azure Synapse Link, work around this issue by creating two or more profiles that contain less than 1,000 tables. <br><br> Expect to select more than 1,000 tables in Fabric Link and in an Azure Synapse Link profile in a future update.| 
+| Export more than 1,000 tables via Azure Synapse Link or add more than 1,000 tables to Fabric link. |  If you're using Azure Synapse Link, work around this issue by creating two or more profiles that contain less than 1,000 tables. <br><br> Expect to select more than 1,000 tables in Fabric link and in an Azure Synapse Link profile in a future update.| 
 | Finance and operations apps tables included in an Azure Synapse Link profile can't be migrated to a different environment using the import and export profile feature in Azure Synapse Link. | Until this issue is addressed, add the same tables into the new environment. Copy and paste a comma separated list of tables into the search box within the manage tables option to select a list of tables at once.  |
 | Azure Synapse Link or Fabric link enables tables where the change tracking property is enabled. <br> Currently, change tracking can't be enabled for all finance and operations entities. The **Track changes** option is unavailable for entities created in finance and operations in the past for data migration. <br> In some entities, enabling change tracking might fail with the error message **chosen entity doesn't pass the validation rules** or the **Track changes** checkbox is disabled for some entities. <br> For more information about entity validation rules and how you can fix them, go to [Enable row version change tracking for data entities](/dynamics365/fin-ops-core/dev-itpro/data-entities/rowversion-change-track#enable-row-version-change-tracking-for-data-entities). You might need developer assistance to complete the steps. | If the chosen entity is unavailable because of the change tracking limitation, choose the tables that comprise the data from that entity. <br> You can use [EntityUtil](https://github.com/microsoft/Dynamics-365-FastTrack-Implementation-Assets/tree/master/Analytics/DataverseLink/DataIntegration/EntityUtil) solution provided by the FastTrack team to create entity shapes using tables. |
 | In case of a database restore operation in Dataverse, finance and operations entities enabled in Azure Synapse Link are removed. | To re-enable entities, re-enable the corresponding virtual tables for all selected entities, re-enable change tracking, and reselect the tables in Azure Synapse Link. You can copy and paste a comma separated list of tables into the search box within the manage tables option to select a list of tables at once.|