Skip to content

Commit a15ef34

Browse files
committed
Support custom partitionid for Dataverse sink
1 parent f705ec4 commit a15ef34

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/data-factory/connector-dynamics-crm-office-365.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -433,6 +433,8 @@ The optimal combination of **writeBatchSize** and **parallelCopies** depends on
433433
]
434434
```
435435

436+
Support specifying the `partitionid` when copying data to Dataverse using the import schemas, you can specify the `partitionid` by referring to this [article](https://learn.microsoft.com/power-apps/developer/data-platform/use-elastic-tables?tabs=sdk#specify-partitionid). Specifying a `partitionId` is optional. If you choose to use a partitioning strategy for Dataverse elastic tables, `partitionid` must be used to uniquely identify a record with primary key. For more information about elastic tables, see the [article](https://learn.microsoft.com/power-apps/developer/data-platform/elastic-tables#partitioning-and-horizontal-scaling).
437+
436438
## Retrieving data from views
437439

438440
To retrieve data from Dynamics views, you need to get the saved query of the view, and use the query to get the data.

0 commit comments

Comments
 (0)