Skip to content

Commit 3108868

Browse files
authored
Update connector-dynamics-crm-office-365.md
1 parent 3012999 commit 3108868

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

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

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -500,6 +500,15 @@ To write data into a lookup field with multiple targets like Customer and Owner,
500500

501501
1. Map both the value and entity-reference columns from source to sink. The entity-reference column must be mapped to a virtual column with the special naming pattern `{lookup_field_name}@EntityReference`. The column doesn't actually exist in Dynamics. It's used to indicate this column is the metadata column of the given multitarget lookup field.
502502

503+
### Setting the Owner field
504+
505+
When setting the Owner field in Dynamics 365 (Microsoft Dataverse) or Dynamics CRM, it is important to provide a valid reference. The valid options for the `@EntityReference` are:
506+
507+
- `systemuser`: This refers to an individual user within the system.
508+
- `team`: This refers to a team of users within the organization.
509+
510+
Ensure that the value provided corresponds to one of these options to avoid errors during data transformation.
511+
503512
For example, assume the source has these two columns:
504513

505514
- **CustomerField** column of type **GUID**, which is the primary key value of the target entity in Dynamics.

0 commit comments

Comments
 (0)