Setup

How to use Entity Reference Fields?

Some fields like the default createdby are entity reference fields, these can also be custom fields which link to a single other record in Dynamics.

For these fields the adapter returns 3 values:

fieldName - This returns the serialized answer from Dynamics. This is a json string with the id, the entity reference type (aka logical name) and some other infos depending on the reference.
fieldName__entityId - The id of the linked record
fieldName__entityName - The type of the linked record (e.g. account, user, …)

To create/update the value of the field the fieldName__entityId value is required. If the field allows multiple types to be referenced also the fieldName__entityName is needed. For create/update the value of fieldName is ignored.

How to use Marketing List?

At least two plans should be set up if marketing list should be managed.

A plan to create/update the contacts
Options:
```
Module: contact
```
This plan supports the use of mass updates to manage a lot of entities at once.
A plan to create/update the marketing lists and to assigning the members to the list
Options:
```
Module: contact
List Adapter: true
```
The Module for this plan needs to be the type of the members in the list. Each list only supports one type of members, either contact, lead or company. Other types for list members are not supported by Dynamics.
There is a field emailAddressListMembers which should have all emails of the contacts separated by a comma.
Other fields of this plan will be set to the list itself (e.g. name)
This plan is optimized for few lists with a lot of members.

CAUTION
If members are not created before there will be only a log message that the member couldn’t be added to marketing list.

To find the entity emailaddress1 is used from Dynamics (first plan)