Merge pull request #296656 from Lucky-Wang16/0320-Dataverse_support_partitionid

prmerger-automator[bot] · web-flow · commit ec1617e9a058 · 2025-04-11T09:32:02.000Z
Update Dataverse custom partitionid write
diff --git a/articles/data-factory/connector-dynamics-crm-office-365.md b/articles/data-factory/connector-dynamics-crm-office-365.md
@@ -433,6 +433,10 @@ The optimal combination of **writeBatchSize** and **parallelCopies** depends on
 ]
 ```
 
+When you select an [elastic tables](/power-apps/developer/data-platform/elastic-tables#partitioning-and-horizontal-scaling) in the copy activity sink, the connector mapping supports the `partitionid` column. You can map your source data column to the sink's `partitionid` column. If not mapped, the primary key value is used as the default value for the `partitionid` column.
+
+`partitionid` can be used in Dataverse alternate keys or primary key scenarios on the write path. Each elastic table contains a system-defined `partitionid` column and has an alternate key named `KeyForNoSqlEntityWithPKPartitionId`, which combines the primary key of the table with the `partitionid` column. For more information, see this [article](/power-apps/developer/data-platform/elastic-tables).
+
 ## Retrieving data from views
 
 To retrieve data from Dynamics views, you need to get the saved query of the view, and use the query to get the data.

Original file line number	Diff line number	Diff line change
`@@ -433,6 +433,10 @@ The optimal combination of writeBatchSize and parallelCopies depends on`
`433`	`433`	`]`
`434`	`434`	```
`435`	`435`
	`436`	+When you select an [elastic tables](/power-apps/developer/data-platform/elastic-tables#partitioning-and-horizontal-scaling) in the copy activity sink, the connector mapping supports the `partitionid` column. You can map your source data column to the sink's `partitionid` column. If not mapped, the primary key value is used as the default value for the `partitionid` column.
	`437`	`+`
	`438`	+`partitionid` can be used in Dataverse alternate keys or primary key scenarios on the write path. Each elastic table contains a system-defined `partitionid` column and has an alternate key named `KeyForNoSqlEntityWithPKPartitionId`, which combines the primary key of the table with the `partitionid` column. For more information, see this [article](/power-apps/developer/data-platform/elastic-tables).
	`439`	`+`
`436`	`440`	`## Retrieving data from views`
`437`	`441`
`438`	`442`	`To retrieve data from Dynamics views, you need to get the saved query of the view, and use the query to get the data.`