You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/data-factory/connector-dynamics-crm-office-365.md
+25-1Lines changed: 25 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.topic: conceptual
8
8
ms.author: jianleishen
9
9
author: jianleishen
10
10
ms.custom: synapse
11
-
ms.date: 06/01/2022
11
+
ms.date: 08/19/2022
12
12
---
13
13
# Copy and transform data in Dynamics 365 (Microsoft Dataverse) or Dynamics CRM using Azure Data Factory or Azure Synapse Analytics
14
14
@@ -509,6 +509,29 @@ If all of your source records map to the same target entity and your source data
509
509
510
510
:::image type="content" source="./media/connector-dynamics-crm-office-365/connector-dynamics-add-entity-reference-column.png" alt-text="Dynamics lookup-field adding an entity-reference column":::
511
511
512
+
## Writing data to a lookup field via alternative keys
513
+
514
+
To write data into a lookup field using alternate key columns, follow this guidance and example:
515
+
516
+
1. Ensure your source contains all the lookup key columns.
517
+
518
+
2. The alternate key columns must be mapped to the column with the special naming pattern `{lookup_field_name}@{alternate_key_column_name}`. The column doesn't exist in Dynamics. It's used to indicate that this column is used to look up the record in the target entity.
519
+
520
+
3. Go to **Mapping** tab in the sink transformation of mapping data flows. Select the alternate key as output columns under the Lookup field. The value after indicates the key columns of this alternate key.
4. Once selected, the alternate key columns will automatically display in below.
525
+
526
+
:::image type="content" source="./media/connector-dynamics-crm-office-365/connector-dynamics-lookup-field-column-mapping-alternate-key-1.png" alt-text="Screenshot shows mapping columns to lookup fields via alternate keys step 1.":::
527
+
528
+
5. Map your input columns on left with the output columns.
529
+
530
+
:::image type="content" source="./media/connector-dynamics-crm-office-365/connector-dynamics-lookup-field-column-mapping-alternate-key-2.png" alt-text="Screenshot shows mapping columns to lookup fields via alternate keys step 2.":::
531
+
532
+
> [!Note]
533
+
> Currently this is only supported in mapping data flows.
534
+
512
535
## Mapping data flow properties
513
536
514
537
When transforming data in mapping data flow, you can read from and write to tables in Dynamics. For more information, see the [source transformation](data-flow-source.md) and [sink transformation](data-flow-sink.md) in mapping data flows. You can choose to use a Dynamics dataset or an [inline dataset](data-flow-source.md#inline-datasets) as source and sink type.
0 commit comments