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 NAV connector. Push are the methods where interworks.cloud platform sends information to NAV and pull are the methods where we get information from NAV. For each method the data transformation schema is explained.


PushPull

CreateUpdateDeleteCreateUpdate
Account


Contact




Product




Invoice




Invoice Items




Orders




Order Items




Payments


Pre Synchronization actions for all Methods


In order to update an entity on MS Dynamics, ETag property is mandatory. This value is automatically fetched before every update action, by using the already defined preSynchronization actions. 

Two actions are implemented in order to store the value inside the request body and if-Match header.


Post Synchronization actions for all Methods


Because MS Dynamics NAV do not support adding an Invoice or Order along with the Items, a postSyncrhonization action is implemented to Invoice and Order modules in order to automatically synchronize their Items after the successful synchronization.


Properties Mappings


BSS Account Address
Due to multiple addresses in a BSS Account, Integration Framework always used the billing address of the account for synchronization


Account Entity

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


Below table presents property mapping between BSS Account entity and MS Dynamics NAV Customer page

Account (BSS module)Customer (Navision Page)
NameName
CreditLimitAmountCredit_Limit_LCY
PhonePhone_No
Address1Address
Address2Address_2
PostCodePost_Code
CityCity
CountryCodeCountry_Region_Code
CorpEmailCorp_Email
WebSiteHome_Page
ServerVariable
Gen_Bus_Posting_Group
Gen_Bus_Posting_Group
ServerVariable Customer_Bus_Posting_GroupCustomer_Bus_Posting_Group
ServerVariable VAT_Bus_Posting_GroupVAT_Bus_Posting_Group
AccounCurrency.Current.MnemonicCurrency_Code


Contact Entity

For BSS contact entities we support only push method.


Below table presents property mapping between BSS Contact and MS Dynamics NAV ContactCard page

Contact (BSS module)ContactCard (Navision Page)
NameName
Person if contact includes an Account or Company otherwiseType
EmailE_Mail
FirstNameSearch_Name
Address1Address
Address2Address_2
PostCodePost_Code
CityCity
CountryCodeCountry_Region_Code
PhonePhone_No
MobilePhoneMobile_Phone_No
Account.AccounCurrency.Current.MnemonicCurrency_Code


Invoice Entity

For BSS Invoice entity we support only push method.


Below table presents property mapping between BSS Invoice and MS Dynamics NAV SalesInvoice page

Invoice (BSS module)SalesInvoice (Navision Page)
"Invoice"Document_Type
Account.NameSell_to_Customer_Name
Account.Address1Sell_to_Address
Account.Address2Sell_to_Address_2
Account.PostCodeSell_to_Post_Code
Account.CitySell_to_City
CreatedAtDocument_Date
DueDateDue_Date
BillingAccount.AccountCurrency.Currency.MnemonicCurrency_Code
"Default(Customer)"BillToOptions
BillingAccount.NameBill_to_Name
BillingAccount.AddressBill_to_Address
BillingAccount.Address2Bill_to_Address_2
BillingAccount.PostCodeBill_to_Post_Code
BillingAccount.CityBill_to_City


Invoice Item Entity

For BSS Invoice Item entities we support only push method.


Below table presents property mapping between BSS Invoice Items and MS Dynamics NAV SalesInvoiceSalesLines page

Invoice Item (BSS module)

SalesInvoiceSalesLines (Navision Page)

"Invoice"Document_Type
Invoice.IntegrationIdDocument_No
"Item"Type
Product.NameDescription
Product.IntegrationIdNo
UnitPriceUnit_Price
QuantityQuantity
DiscountLine_Discount_Percent


Order Entity

For BSS Order entity we support only push method.

Below table presents property mapping between BSS Order and MS Dynamics NAV SalesOrder page

Order (BSS module)SalesOrder (Navision Page)
"Order"Document_Type
Account.NameSell_to_Customer_Name
Account.Address1Sell_to_Address
Account.Address2Sell_to_Address_2
Account.PostCodeSell_to_Post_Code
Account.CitySell_to_City
CreatedAtDocument_Date
DateOrder_Date
Account.AccountCurrency.Currency.MnemonicCurrency_Code
"Default(Customer)"BillToOptions
Account.NameBill_to_Name
Account.AddressBill_to_Address
Account.Address2Bill_to_Address_2
Account.PostCodeBill_to_Post_Code
Account.CityBill_to_City


Order Item Entity

For BSS Invoice Item entities we support only push method.


Below table presents property mapping between BSS Invoice Items and MS Dynamics NAV SalesInvoiceSalesLines page

Invoice Item (BSS module)

SalesInvoiceSalesLines (Navision Page)

"Invoice"Document_Type
Order.IntegrationIdDocument_No
"Item"Type
Product.NameDescription
Product.IntegrationIdNo
DiscountLine_Discount_Percent


Product Entity

For BSS Product entities we support only push method.


Below table presents property mapping between BSS Product and MS Dynamics NAV ItemCard page

Product (BSS module)

Item Card (Navision Page)

NameDescription
"Service"Type
UnitType.NameBase_Unit_of_Measure
ShortDescriptionSearch_Description
IsEnabled (opposite value)Blocked

ServerVariable
Gen_Prod_Posting_Group

Gen_Prod_Posting_Group

ServerVariable
VATA_Prod_Posting_Group

Vat_Prod_Posting_Group


Payment Entity

For BSS Payment entities we support both push and pull method.


Below table presents property mapping between BSS Payment and MS Dynamics NAV PaymentJournal page for push method

Payment (BSS module)

Payment Journal (Navision Page)

PaymentDatePostin_Date
"Payment"Document_Type
"Customer"Account_Type
Account.IntegrationIdAccount_No
Method.IntegrationIdPayment_Metho_Code
Account.AccountCurrency.Currency.MnemonicCurrency_Code

ServerVariable
Bal_Account_No

Bal_Account_No
ServerVariable
BalAccName
Bal_Account_Name
ServerVriable
Bal_Account_Type
Bal_Account_Type

Below table presents property mapping between BSS Payment and MS Dynamics NAV CustomerLedger page for pull method

Payment (BSS module)Customer Ledger (Navision Page)
AccountIdCustomer_No
DueDateDue_Date
PaymentDatePosting_Date
State"p"
SendConfirmation"False"
AmountAmount

Table of Contents


  • No labels