Mapping
✍️ DRAFT : IN PROGRESS
Contact details, among other things, are synced between Dynamics 365 and Spotler. A mapping describes which fields of Dynamics 365 maps with the fields in Spotler.
We will configure a simple default mapping and email the initial configuration of the mapping in an Excel document.
The mapping is stored in the AutomateValue Connector Platform and managed by AutomateValue. Changes can be requested by email (support@automatevalue.com).
Think about the fields do you want to map between both systems and let us know. Often it is useful to have a session with each other about what is possible and which fields you want to synchronize to Spotler.
Please note that fields may not be more than one level deep. For example, fields from Account can be included in the Contact synchronization, because that is one level (Contact->Account). It is also useful to think about which entities need to be synchronized: only Contact or Contact and Lead? Are all contacts allowed to go to Spotler or only with certain characteristics?
Datatype Conversions
Mapping row options
The mapping row needs the following params:
| Field | Value | Remark |
|---|---|---|
| Contact Column | columnname | Contact field to map to in Dataverse |
| Lead Column | columnname | Lead field to map to in Dataverse |
| Account Column | columnname | Account field to map to in Dataverse |
| Entity Column | columnname | MembershipEntry field to map to in Dataverse |
| Sync Direction | ->, <- or <-> | Allowed direction to sync data |
| Filter | filtervalue | Only allow sync when column has this value |
| Spotler Column | fieldname | Field to map to in Spotler |
Instead of a column or field name you can also use the following special values:
| Special Value | Description |
|---|---|
| $CustomerType | The source entity type: contact, lead or account. |
| $value:PRD | Set hardcoded value, like PRD |
| @map(permissions) | Map to Permission entity |
| @map(list) | Map to Marketing List |
| @map(periodiek) | Map to Periodiek in iFund Engage365 |
| columname(relatedEntityType). columnnameOfRelatedEntity | Map column of related entity, for example 'parentcustomerid(account).accountnumber' or 'ownerid(systemuser).fullname'. Max distance is 1 relationship. |
| column1;column2; | Select first not-null column value, for example 'address1_line1;address1_line2;address1_line3' |
Future ideas for special values:
| Special Value | Description |
|---|---|
| @concat(column1, " ", column2) | Concat given column values and/or hard coded values, for example '@concat(address1_line1, ", ", address1_line2)' |
| @child(dh_permissions).first(createdOn DESC).name | Select column of first child record (params: table, column-result, column-match-id, sortby) |
| @odata:odata-query | Run odata query and use value, for example '@oadata:contacts?$select=fullname&$filter=(_parentcustomerid_value eq $ID and statecode eq 0)&$orderby=createdon desc&$top=1' |