Search

Page tree
Skip to end of metadata
Go to start of metadata

This page explains which are the Push and Pull methods supported by MS Dynamics 365 CE connector. Push are the methods where interworks.cloud platform sends information to CRM and pull are the methods where we get information from CRM. For each method the data transformation schema is explained.


Push

Pull


Create

Update

Delete

Create

Update

Account


Contact


Product




Invoice




Invoice Items




Orders




Order Items




Cases


Pre Synchronization actions for all Methods


For update operation ETag property if set in the pre-synchronization action


Post Synchronization actions for all Methods


Because MS Dynamics 365 CE does not support adding an Invoice along with the Items, a postSynchronization action is implemented to Invoice module in order to automatically synchronize their Items after the successful synchronization.


Properties Mappings


Account Entity

For BSS Accounts entities will support both push and pull methods.


Below table presents property mapping between BSS Account entity and Dynamics 365/2016 Account

Account(BSS)

Account(Dynamics 365/2016)

Comment

integrationId

accountid

auto generate

name

name


webSite

websiteurl


phone

telephone1


fax

fax


description

description


creditLimitAmount

creditlimit


industry

industrycode

The mapping for the Industry lookup will be used

currency

transactioncurrencyid@odata.bind
_transactioncurrencyid_value (for Pull)

"transactioncurrencyid@odata.bind": "/transactioncurrencies(1bd53eb3-1181-e911-80be-00155d091ce2)"
Currency needs to be mapped in lookup in connector setting page

addresses.address1

address1_line1


addresses.address2

address1_line2


addresses.city

address1_city


addresses.region

address1_country


addresses. postCode

address1_postalcode


addresses. stateName

address1_stateorprovince


addresses.countryName

address1_country


account.ParentAccount.integrationId

parentaccountid@odata.bind


Contact Entity

For BSS Contacts entities we support both push and pull methods.


Below table presents property mapping between BSS Contact entity and Dynamics 365 CE Contact

Contact(BSS)

Contact(Dynamics 365/2016)

Comment

integrationId

contactid

Auto generate

lastName

lastname


firstName

firstname


mobilePhone

mobilephone


phone

telephone1


fax

fax


email

emailaddress1


jobTitle

Jobtitle


account.integrationId

parentcustomerid_account@odata.bind
_parentcustomerid_value (for Pull)


Product Entity

For BSS Product entities we support only push method.


Below table presents property mapping between BSS Product entity and Dynamics 365 CE Product

Product (BSS)

Product (Dynamics 365/2016)

Comment

integrationId

productid

Autogenerate

productType

parentproductid@odata.bind

On BSS product type is the product family in CRM
"/products(a4b7a5e4-5281-e911-80bf-00155d091ce2)"

name

name


code

productnumber


numberOfDecimals

quantitydecimal


isProductGroup

productstructure


fullDescription

description


NA

defaultuomscheduleid@odata.bind

Default unit group for the product.
"defaultuomscheduleid@odata.bind": "/uomschedules(30999669-cd6f-4e37-9ee5-635c36a19143)" Server variable

NA

defaultuomid@odata.bind

Default unit for the product.
"defaultuomid@odata.bind": "/uoms(2bf179d5-c7ab-4d74-aaa3-7d268178d23e)",
Server variable

Order Entity

For BSS Order entity we support only push method


Below table presents property mapping between BSS Order entity and Dynamics 365 CE SalesOrder

Order(BSS)

SalesOrder(Dynamics 365/2016)

Comment

integrationId

salesorderid

Auto generate CRM

name

name


description

description


account

customerid_account@odata.bind


contact

customerid_contact@odata.bind


Account.Name

shipto_name


Account.Address1

shipto_line1


Account.Address2

shipto_line2


Account.PostCode

shipto_postalcode


Account.City

shipto_city


BillingAccount.AccountCurrency.

Currency.Mnemonic

transactioncurrencyid_value@odata.bind


BillingAccount.Name

billto_name


BillingAccount.Address

billto_line1


BillingAccount.Address2

billto_line2


BillingAccount.PostCode

billto_postalcode


BillingAccount.City

billto_city


Order Item Entity

Order Items(BSS)

SalesOrderDetails (Dynamics 365/2016)

Comment

integrationId

salesorderdetailid

Auto generate CRM

order

salesorderid@odata.bind

"salesorderid@odata.bind": "/salesorders(11f1fd29-e288-e911-80c0-00155d091ce2)"
parent salesorderid

product

productid@odata.bind

"productid@odata.bind": "/products(4b5aab6d-4b87e91180c000155d091ce2)"

NA

uomid@odata.bind

PrimaryUnit guid, this will be taken from server variable

Invoice Entity

For BSS Invoice entity we support only push method.


Invoices(BSS)

Invoices(Dynamics 365/2016)

Comment

integrationId

invoiceid

Auto generated by CRM

stage.integrationId

statecode

The mapping from Order Stage lookup will be used

account

customerid_account@odata.bind

"customerid_account@odata.bind": "/accounts(4c344e51-ce85-e911-80c0-00155d091ce2)"

Account.Name

shipto_name


Account.Address1

shipto_line1


Account.Address2

shipto_line2


Account.PostCode

shipto_postalcode


Account.City

shipto_city


BillingAccount.AccountCurrency.Currency.Mnemonic

transactioncurrencyid_value@odata.bind


BillingAccount.Name

billto_name


BillingAccount.Address

billto_line1


BillingAccount.Address2

billto_line2


BillingAccount.PostCode

billto_postalcode


BillingAccount.City

billto_city


NA

pricelevelid@odata.bind

This (Price List) required property hence it is set at server variable

Invoice Item Entity

For BSS Invoice Item entities will support only push method.

InvoiceItem(BSS)

InvoiceDetails(Dynamics 365/2016)

Comment

integrationId

invoiceid

Auto generated in CRM

invoice

invoiceid@odata.bind

specify parent invoiceid

product

productid@odata.bind


unit

uomid@odata.bind


quantity

quantity


unitPrice

priceperunit


Case Entity

For BSS cases entity we support both push and pull method.

Case(BSS)

Incident(Dynamics 365/2016)

Comment

integrationId

incidentid

Auto generate CRM

account

customerid_account@odata.bind
_accountid_value (for Pull)


contact

customerid_contact@odata.bind
_contactid_value (for Pull)


Stage. id

servicestage

The mapping for "Case Stage" lookup will be used


Type.integrationId

casetypecode

The mapping for "Case Type" lookup will be used

Priority.integrationId

prioritycode

The mapping for "Case Priority" lookup will be used

name

title


description

description


parent

parentcaseide@odata.bind
_parentcaseid_value (for Pull)


product

productid@odata.bind

This is not supported in pull



Table of Contents


  • No labels