Map Type Definitions and Order

Map IDs provide a basic understanding of what the map does:

• Map ID’s beginning with ‘NAV_’ send data into NAV
• Map ID’s beginning with ‘SF_’ send data into Salesforce
• Map ID’s ending with ‘_BK’ are bulk maps meant to be run once to initially sync both systems
• Map ID’s ending with ‘_CH’ are change-based maps meant to be run on an ongoing basis. These maps can be scheduled to run every day.

The bulk maps are designed to be run before the change-based maps, and the change-based maps can all be scheduled.  The ‘SF_OPP_INVOICE_ONGOING’, which is linked to the ‘NAV_INVOICE_OPP_BK’ map, doesn’t need to be ran by hand.

Map List with Descriptions

The table below lists all the maps in this set of templates.

Setup Overview

System Prerequisites

To use the templates, the following software must be installed and ready to use:

• A valid Dynamics NAV 2017 install*
• A valid SalesForce instance/organization
• SmartConnect 20.17.0.17 or higher

* The ‘NAV_INVOICE_OPP_BK’ maps ‘Sell To Customer Name’, but NAV 2016 needs the ‘No’ field mapped instead of the ‘Sell To Customer Name’ field.

ERP Customizations and Installations

Dynamics NAV

Dynamics NAV web pages must be published for SmartConnect to send or receive data from them.  The following is a list of NAV pages that must be published:

Salesforce

Opportunities in Salesforce have a custom text field to hold the name of the Dynamics NAV Invoice number.  The field name is ‘NAV_Invoice_Number’ and the data type is Text(21).

Add this custom field to the NAV Opportunity.

SmartConnect setup

With both services running, set up the connector for both services so SmartConnect knows how to reach them.

Salesforce

In the main SmartConnect window, click the Setup ribbon and the Setup button.  On the SmartConnect Setup window, open the SalesForce Connector.

Click the ‘Activate Connector’ button at the top of the Salesforce Connector Setup window.

The Salesforce window needs a username, password, and user security token from Salesforce.  The username is the email address, the password is the user’s password, and the security token is the user’s security token.

To find the security token in Salesforce, click the ‘My Settings’ button from the username drop-down in the top-right of the Salesforce interface.

Click the link to edit personal information.

Click the ‘Reset My Security Token’ link on the far left side of the interface.  Follow the prompts to find your security token and paste it into the Salesforce Connector Setup window.  Below is an example of a filled-out connector.

Dynamics NAV

The setup for NAV requires the service URL, domain, username and password, and default company.  Below is an example of a filled-out connector.

SmartConnect Map Import

Import the maps by clicking the Maintenance tab on the ribbon and clicking the ‘Import Wizard’ button.  Browse to the ‘Salesforce NAV Maps.sce’ file from the zipped folder in the window that appears.  Follow through the wizard to import the maps.

Map Run Overview

Choosing the Correct Maps to Use

Not all maps will be used by an organization.  Because there are maps sending data into either Dynamics NAV or Salesforce, choose the maps that best fit your organization structure.  For example, if you create items in NAV, you won’t need NAV_ITEM_BK (which sends products from Salesforce into NAV) but you will use the SF_ITEM_BK map (which sends items from NAV into Salesforce).

 Ongoing Maps and schedule intervals

Once you rule out which bulk maps to run, decide how you want SmartConnect to keep both systems in sync.  The change-based maps (ending in ‘_CH’) are very similar to the bulk versions of the map, but only send records that have been created recently.  For example, the ‘SF_CUSTOMERS_CH’ map will only create customers that have been created in the previous day by filtering on the ‘Last_Date_Modified’ field.

To keep the systems in sync, this map can be scheduled to run once a day every day.  All of the change based maps use this type of filter, so they are good candidates for scheduling.  This can be changed to run more often, but the templates filter by TODAY by default.

Default Values

Salesforce and Dynamics NAV contain different levels of detail on each object, so some defaults must be hard-coded.  For example, items in NAV will have several posting groups associated with the item, but posting groups don’t exist in Salesforce by default.  For objects that have required fields in NAV but do not have an obvious field in Salesforce to map to it, a local constant is set.  The constants were chosen based off sample data, BUT SHOULD BE CHANGED TO FIT YOUR INTEGRATION REQUIREMENTS!

Below is a list of maps that have local constants defined.