Notice

The below provided instructions are our general ruleset for upgrading or migrating a Dynamics GP system with the use of our Standard/Advance integration utilizing eConnect. TrueCommerce is not responsible for your server migration, and while we are able to assist in the process, require a 2-week prior notice for proper availability.

Step 1. Installation of GP & eConnect

Prior to TrueCommerce being able to assist - you'll need to install or upgrade you'll need to install the additional component known as eConnect which comes with the installer for GP. If you are in need of assistance getting this installed, please contact your VAR

Installation of eConnect

Each version of GP has its own installation of eConnect (for example GP2015 and GP2018 each have their own version of eConnect that works with that specific version)
Required on all client machines
eConnect Service must have permission to SQL Server

Step 2. Installation of the Integration Service (Server + All Clients)

The Integration Service primarily role is to communicate Dynamics GP with Transaction Manager (through the eConnect service) - however it also includes all the setup files for both the SQL Server as well as the GP Server.

ALWAYS BACKUP YOUR CURRENT DLL IF UPDATING AN EXISTING SERVER

Always backup the original Tc.Int.Platform.BSPDynamicsGP.dll to a safe location BEFORE installing the integration service or replacing the DLL manually

LOCATION: C:\Program Files (x86)\True Commerce\TmoIntegrationService\

First you'll want to download and install the Integration Service

Installing Integration Service

Step 3. Running the Dynamics Integration Setup

Your system should automatically detect Dynamics GP if installed on the machine, and auto-prompt you with the Dynamics GP installation portion that is attached to the Integration Service - should it not; you can navigate to C:\Program Files (x86)\True Commerce\TmoIntegrationService\Dynamics

if the Dynamics setup.exe is missing - you can download it manually here

This will extract the SQL Stored Procedures to the TmoIntegrationService folder along with additional components to install (see below)

Step 4. Creating the SQL Server's Stored Procedures - TM_DymanicsGP_db.sql

Once setup.exe is ran, you'll find a DynamicsGP folder within the TmoIntegrationService folder - with various subdirectories for each version of GP.

Execute the TM_DynamicsGP_db.sql on your SQL Server

These are the TrueCommerce Stored Procedures and do not modify any company/system tables

Step 5. Creating the SQL Server's Stored Procedures - Extended

Once complete, you'll need to run the remaining 4 procedures located within your respective GP version subfolder (e.g: 2015 for GP2015)

WARNING : THESE OVERWRITE THE NATIVE DYNAMICS GP PROCEDURES - ANY CUSTOMIZATIONS WILL BE LOST - ALWAYS CONSULT YOUR VAR/IT IF YOU BELIEVE YOU HAVE CUSTOMIZATIONS
TrueCommerce is not responsible for any loss of customizations to these procedures

Step 6. Run EXEC DmCreateProcs

Once all the Stored Procedures are ran from the folders, run your SQL Management software and run the command EXEC DmCreateProcs against your Dynamics GP Company database - which will complete the installation of all the generated Stored Procedures.

EXEC DmCreateProcs

Step 7. Install the ASN.cnk file (Clients)

Any client wishing to use the ASN module within TrueCommerce needs to install the dictionary for GP for the extended model - simply place the ASN.cnk inside the root installation folder for GP and run Dynamics GP with "Run As Admin" command - the system will prompt you to install new code, select yes to install the ASN module (recommend doing this as local admin)

Log in as the SA user within Dynamics GP and navigate to a Sales Transaction Entry (any will do, does not need to be an EDI specific order) and select Additional → ASN to let the module initialize - once complete any non-sa user should be able to easily launch this module without issue.

Step 8. Update Transaction Manager Integration Options (Optional)

If you've moved to a new SQL Server, the Transaction Manager platform will need to be pointed to the new server. Log into Foundry and

Navigate: Business System section → Company Configuration → Integraiton Options

Fill: The SQL Server & GP Database sections

Server : The SQL Server path to your new server
GP Database: Name of the Company Database for GP
User: The user who will have access to the company database
Password: Password for user

Step 9. Restart Integration Service

Restarting the integration service will refresh any previously used DLL and allow the new one to get attached.

Restarting the Integration Service

11/21/22