Integration Manager Sales Order Integration – “The Sales Intrastat Entry window is open”

● Ian Grieve ●  ● 1 Comment   ● 

Microsoft Dynamics GPJust before Christmas I was creating an integration for a client in Integration Manager which would integrate Sales Orders, but unfortunately I was receiving an error message:

Integration Log
Integration: Eriks SO Integration (ID: 8)
Action: None
Start Time: 23/12/2016 11:05:38

  23/12/2016 11:05:38 Source: IIntegrationEngine_Run, Status Code: 0    Opening source query...
  23/12/2016 11:05:38 Source: IIntegrationEngine_Run, Status Code: 0    Initializing Source...
  23/12/2016 11:05:38 Source: IIntegrationEngine_Run, Status Code: 0    Establishing source record count...
  23/12/2016 11:05:38 Source: IIntegrationEngine_Run, Status Code: 0    Beginning integration...
1:  Order  Insert Failed 5. Seconds 
    DOC 1 ERROR: The Sales Intrastat Entry window is open. - The Sales Intrastat Entry window is open.
  23/12/2016 11:05:43 Source: FinishIntegration, Status Code: 3    Integration Failed
  23/12/2016 11:05:43 Source: FinishIntegration, Status Code: 3    Integration Results
    1 documents were read from the source query.
    1 documents were attempted:
        0 integrated without warnings.
        0 integrated with warnings.
        1 failed to integrate.

Finish Time: 23/12/2016 11:05:43

Source Total: 1
Successfully Integrated: 0
Integrated With Warning: 0
Failed: 1

Completion Status: Completed
Integration Status: No Documents Succeeded

Continue reading → Integration Manager Sales Order Integration – “The Sales Intrastat Entry window is open”

● Categories: Dynamics, GP, Intrastat, Microsoft ● Tags: , , , , , , , , ,  ● Permalink ● Shortlink ●

Hands On With Microsoft Dynamics GP 2016 R2: Integration Manager First Run

● Ian Grieve ●  ● 3 Comments   ● 

Microsoft Dynamics GPWith the release of Microsoft Dynamics GP 2016 R2 it’s time for a series of “hands on” posts where I go through the installation of all of it’s components; the index for this series can be found here.

The first time you run Integration Manager after installation, you need to right click and Run as Administrator. This makes sure that all of the relevant registry entries are created:

Integration Manager on the Start menu

Continue reading → Hands On With Microsoft Dynamics GP 2016 R2: Integration Manager First Run

● Categories: Dynamics, GP, Integration Manager, Microsoft ● Tags: , , , , , , , , ,  ● Permalink ● Shortlink ●

Hands On With Microsoft Dynamics GP 2016 R2: Install Integration Manager

● Ian Grieve ●  ● 4 Comments   ● 

Microsoft Dynamics GPWith the release of Microsoft Dynamics GP 2016 R2 it’s time for a series of “hands on” posts where I go through the installation of all of it’s components; the index for this series can be found here.

With eConnect installed I can now install Integration Manager with both sets of adapters (Dynamics GP and eConnect).

To do this launch the setup utility from the installation media and, under Additional Products click on Integration Manager:

Microsoft Dynamics GP 2016 Setup Utility

Continue reading → Hands On With Microsoft Dynamics GP 2016 R2: Install Integration Manager

● Categories: Dynamics, eConnect, GP, Integration Manager, Microsoft ● Tags: , , , , , , , ,  ● Permalink ● Shortlink ●

VBA for Integration Manager to Insert Vendor EFT Bank And Email Addresses

● Ian Grieve ●  ● 4 Comments   ● 

Microsoft Dynamics GPI did a SQL Script back in October 2014 which allowed Vendor EFT Details to be inserted, but, if the client is going to run it themselves, requires the assistance of the IT Department as end users don’t usually have access to SQL Server Management Studio.

For most clients, this hasn’t usually been a problem, but a number of the clients I have worked with recently have had multiple projects on the go at the same time. This has meant that while an IT representative can be available, it isn;t usually very timely and can delay UAT.

As such, I wrote some VBA script for Integration Manager which inserts both the Vendor Email and EFT Details. Continue reading → VBA for Integration Manager to Insert Vendor EFT Bank And Email Addresses

● Categories: Dynamics, GP, Integration Manager, Microsoft ● Tags: , , , , , , ,  ● Permalink ● Shortlink ●

Integration Manager Error: Cannot Open Database “GPLIV” Requested By The Login

● Ian Grieve ●  ● 1 Comment   ● 

Microsoft Dynamics GPWe’re in the middle of large upgrade project at the moment for a client and encountered an error when trying to run an integration.

This particular integration is an Account one, which has been extended with VB Script which checks to see if the segments exist, and if not, it inserts them. When a user tried to run the integration, they get the following error:

Opening source query...
Establishing source record count...
Beginning integration...
DOC 1 ERROR: System.Data.SqlClient.SqlError: Cannot open database "GPLIV" requested by the login. The login failed.
DOC 2 ERROR: System.Data.SqlClient.SqlError: Cannot open database "GPLIV" requested by the login. The login failed.
DOC 3 ERROR: System.Data.SqlClient.SqlError: Cannot open database "GPLIV" requested by the login. The login failed.
Integration Failed
Integration Results
    3 documents were read from the source query.
    3 documents were attempted:
        0 integrated without warnings.
        0 integrated with warnings.
        3 failed to integrate.

I did some double checking and it turned out that the user who was doing the testing had two Domain accounts (one with full name and one with initial and surname) and were not using the one I had configured originally.

All of the other users I had worked with had been using Domain accounts of initial and surname, which was the one I had configured, but this particular user was using the account with their full name.

Adding this Domain user account to the database with the DYNGRP role resolved the problem.

● Categories: Dynamics, GP, Integration Manager, Microsoft ● Tags: , , , , ,  ● Permalink ● Shortlink ●

Execute Batch File In Integration Manager

● Ian Grieve ●  ● 4 Comments   ● 

Microsoft Dynamics GPI can’t remember why I created this code, but it allows a batch file to be run from an Integration Manager script:

/*
Created by Ian Grieve of azurecurve|Ramblings of a Dynamics GP Consultant (http://www.azurecurve.co.uk)
This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0 Int).
*/
Set objShell = CreateObject("WScript.Shell")
Set objExec = objShell.Exec("B:\IM.bat")

I’m posting it here so I don’t lose it for when I remember why I write it, and perhaps it may be useful to others.

● Categories: Dynamics, GP, Integration Manager, Microsoft ● Tags: , , , ,  ● Permalink ● Shortlink ●

Integration Manager VBA Script To Create XML Output

● Ian Grieve ●  ● 1 Comment   ● 

Microsoft Dynamics GPWe have a client who will be loading payables transactions into Microsoft Dynamics GP and need secondary postings created into the General Ledgers of other company databases. The idea is to use the AfterDocument script to create and submit an eConnect document, which is in XML format.

The below code is a small proof of concept which creates an XML file with child and parent nodes and saves it to the T:\:

/*
Created by Ian Grieve of azurecurve|Ramblings of a Dynamics GP Consultant (http://www.azurecurve.co.uk)
This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 2.0 UK: England & Wales (CC BY-NC-SA 2.0 UK).
*/
Set xmlDoc = CreateObject("Microsoft.XMLDOM")

Set objRoot = xmlDoc.createElement("RootElement")
xmlDoc.appendChild objRoot

Set objRecord = xmlDoc.createElement("SubLevel1")
objRoot.appendChild objRecord

Set objName = xmlDoc.createElement("Element1")
objName.Text = "AAAAAAA"
objRecord.appendChild objName

Set objDate = xmlDoc.createElement("Element2")
objDate.Text = "BBBBBBB"
objRecord.appendChild objDate

Set objIntro = xmlDoc.createProcessingInstruction ("xml","version='1.0'")
xmlDoc.insertBefore objIntro,xmlDoc.childNodes(0)

xmlDoc.Save "T:\Test.xml"
● Categories: Dynamics, GP, Integration Manager, Microsoft ● Tags: , , , ,  ● Permalink ● Shortlink ●

Hands On With Microsoft Dynamics GP 2016 R1: Integration Manager First Run

● Ian Grieve ●  ● 3 Comments   ● 

Microsoft Dynamics GPOnce Integration Manager has been installed there is a final admin step which is required. Before it can be used, it needs to be run as an admin (to prevent errors) and the registration keys entered.

Find Integration Manager on the Windows start menu, right click and Run as Administrator:

App Search for "integ"

Continue reading → Hands On With Microsoft Dynamics GP 2016 R1: Integration Manager First Run

● Categories: Dynamics, GP, Integration Manager, Microsoft ● Tags: , , , , , , , , , ,  ● Permalink ● Shortlink ●

Hands On With Microsoft Dynamics GP 2016 R1: Integration Manager Installation

● Ian Grieve ●  ● 3 Comments   ● 

Microsoft Dynamics GPNow that we have eConnect is installed we can move onto installing Integration Manager. Do this by starting the setup utility and then under Additional products click Integration Manager:

Integration Manager for Microsoft Dynamics GP 2016

Continue reading → Hands On With Microsoft Dynamics GP 2016 R1: Integration Manager Installation

● Categories: Dynamics, GP, Integration Manager, Microsoft ● Tags: , , , , , , , , ,  ● Permalink ● Shortlink ●

Hands On With Microsoft Dynamics GP 2016 R1: eConnect Installation

● Ian Grieve ●  ● 5 Comments   ● 

Microsoft Dynamics GPMicrosoft Dynamics GP comes with a number of different integration tools such as eConnect and Integration Manager. In this post, I’m going to step through the installation of eConnect so that the eConnect adaptor will be available to Integration Manager.

To install eConnect, launch the setup utility, under Additional products select eConnect:

Microsoft Dynamics GP 2016 Setup Utility

Continue reading → Hands On With Microsoft Dynamics GP 2016 R1: eConnect Installation

● Categories: Dynamics, eConnect, GP, Microsoft ● Tags: , , , , , , , , ,  ● Permalink ● Shortlink ●