Skip to content

Commit eec5fe4

Browse files
authored
Merge pull request #208473 from Clare-Zheng82/0817-Add_Dynamics_Guid_Lookup_feature_doc
Add ‘Writing data to a lookup field via alternative keys’ section
2 parents fce30fa + 239b02e commit eec5fe4

File tree

4 files changed

+25
-1
lines changed

4 files changed

+25
-1
lines changed

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

Lines changed: 25 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.topic: conceptual
88
ms.author: jianleishen
99
author: jianleishen
1010
ms.custom: synapse
11-
ms.date: 06/01/2022
11+
ms.date: 08/19/2022
1212
---
1313
# Copy and transform data in Dynamics 365 (Microsoft Dataverse) or Dynamics CRM using Azure Data Factory or Azure Synapse Analytics
1414

@@ -509,6 +509,29 @@ If all of your source records map to the same target entity and your source data
509509

510510
:::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":::
511511

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.
521+
522+
:::image type="content" source="./media/connector-dynamics-crm-office-365/select-alternate-key-columns.png" alt-text="Screenshot shows selecting alternate key columns.":::
523+
524+
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+
512535
## Mapping data flow properties
513536

514537
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.
@@ -587,6 +610,7 @@ IncomingStream sink(allowSchemaDrift: true,
587610
skipDuplicateMapInputs: true,
588611
skipDuplicateMapOutputs: true) ~> DynamicsSink
589612
```
613+
590614
## Lookup activity properties
591615

592616
To learn details about the properties, see [Lookup activity](control-flow-lookup-activity.md).
Loading
Loading
15 KB
Loading

0 commit comments

Comments
 (0)