Execute Batch File In Integration Manager

● Ian Grieve ●  ● 0 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 ●  ● 0 Comments  ● 

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 ●

eConnect Adapter Error In Integration Manager

● Ian Grieve ●  ● 3 Comments  ● 

Microsoft Dynamics GPA recent upgrade of a client from Microsoft Dynamics GP 2010 R2 to GP 2015 R2 recently resulted in an issue being found when testing some integrations in Integration Manager:

DOC 68 ERROR: eConnect error - The source was not found, but some or all event logs could not be searched.  To create the source, you need permission to read all event logs to make sure that the new source name is unique.  Inaccessible logs: Security.

The problem was a fairly simple one in that the eConnect service account did not have the necessary permissions; a very similar issue to the one I blogged about in March 2013.

The solution is to add the service account to the Local Admins group; instructions are in the post I linked above.

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

Integration Manager Error: Error Executing Script ‘Before Integration’ Line 17: – Object required: ‘gpObj’

● Ian Grieve ●  ● 4 Comments  ● 

Microsoft Dynamics GPOne of Perfect Image’s clients is merging with another organisation and I’ve been onsite a few times to help them configure the new companies and import data. One of the items on my list was to use Integration Manager to import the new chart of accounts. While doing this I used VBA to extend the integration to map between the chart of accounts in the new system to the new format and numbering wanted in Microsoft Dynamics GP.

It was when I came to test the integration with the mapping active that I encountered my problem:

ERROR: Error Executing Script 'Before Integration' Line 17: - Object required: 'gpObj'

Show/Hide Error Message

ERROR: Error Executing Script 'Before Integration' Line 17: - Object required: 'gpObj'
Error Executing Script 'Before Integration' Line 17: - Object required: 'gpObj'
Object required: 'gpObj'
Integration Failed
Integration Results
    0 documents were read from the source query.
    0 documents were attempted:
        0 integrated without warnings.
        0 integrated with warnings.
        0 failed to integrate.

Continue reading → Integration Manager Error: Error Executing Script ‘Before Integration’ Line 17: – Object required: ‘gpObj’

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

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

● Ian Grieve ●  ● 3 Comments  ● 

Microsoft Dynamics GPMicrosoft Dynamics GP 2015 R2 was released at the end of May. As I mentioned at the time, I was away from home for work and rather busy otherwise so this series of posts has been somewhat delayed.

However, I am now getting my hands on GP 2015 R2 and thought I would do my usual set of posts on the installation of the various components and also the usage of the new functionality. This is going to be quite a long series of posts, so keep checking back regularly.

After Integration Manager has been installed on a client machine, the license key needs to be input. Do this by locating the Integration Manager icon on the Start screen, right-click it and select Run as Administrator.

When Integration Manager starts you will be prompted to register now or later; click on Register Now:

Integration Manager: Register Now or Later

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

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

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

● Ian Grieve ●  ● 3 Comments  ● 

Microsoft Dynamics GPMicrosoft Dynamics GP 2015 R2 was released at the end of May. As I mentioned at the time, I was away from home for work and rather busy otherwise so this series of posts has been somewhat delayed.

However, I am now getting my hands on GP 2015 R2 and thought I would do my usual set of posts on the installation of the various components and also the usage of the new functionality. This is going to be quite a long series of posts, so keep checking back regularly.

Integration Manager is a tool which is very useful during an implementation and is also on an ongoing basis for integrating files from other systems or third parties. It is also a very simple install.

To install Integration Manager, run the setup.exe from the downloaded installation media. Under Additional Products click on Integration Manager:

Microsoft Dynamics GP 2015 setup utility

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

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

Integration Manager – Cannot Create ActiveX Component

● Ian Grieve ●  ● 3 Comments  ● 

Microsoft Dynamics GPI’ve probably said this before, but Integration Manager can be both very useful and also most infuriating, because when you get an error the error message usually isn’t useful.

However, my most recent problem with Integration Manager did actually produce a useful error message:

Integration Manager - Integration 'Invoices' is not ready to run due to the following problems: The destination could not be initialized due to the following problem: Cannot create ActiveX component.

Integration Manager

Integration 'Invoices' is not ready to run due to the following problems:
- The destination could not be initialized due to the following problem:

Cannot create ActiveX component.

I did a search and found a most useful KB article from Microsoft which detailed the problem (Microsoft Dynamics GP hadn’t been written to the registry correctly) and also the solution.

I read the whole article and decided to try a shortcut of starting with step 3 of re-registering the Dynamics.exe. To do this open a Run or Command Prompt and type the following (this particular problem was encountered with Microsoft Dynamics GP 20103 R2):

"C:\Program Files (x86)\Microsoft Dynamics\GP2013\Dynamics.exe" /regsrver

When I retried the integration, it ran through without further problems.

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

Integration Manager Syntax Error (Missing Operator) In Query Expression

● Ian Grieve ●  ● 1 Comment  ● 

Microsoft Dynamics GPA client recently logged a problem with our Service Desk to report that an Integration Manager integration wasn’t working; when trying to run the integration they received an error message on every line of the integration:


Opening source query...
Establishing source record count...
Beginning integration...
DOC 1 ERROR: Syntax error (missing operator) in query expression 'UCase(DATE#######) = UCase('' AND [RUN NUMBER] = ')''.
DOC 2 ERROR: Syntax error (missing operator) in query expression 'UCase(DATE#######) = UCase('' AND [RUN NUMBER] = ')''.
.
.
.
DOC 10 ERROR: Syntax error (missing operator) in query expression 'UCase(DATE#######) = UCase('21 January 2015') AND UCase([RUN NUMBER]) = UCase('HP33')'.
DOC 11 ERROR: Syntax error (missing operator) in query expression 'UCase(DATE#######) = UCase('21 January 2015') AND UCase([RUN NUMBER]) = UCase('HP33')'.
ERROR: Max Errors Exceeded at 11, Integration Canceled
ERROR: Integration canceled during document integration.
Integration Failed
Integration Results
    100 documents were read from the source query.
    11 documents were attempted:
        0 integrated without warnings.
        0 integrated with warnings.
        11 failed to integrate.

After doing some debugging of the integration, we identified the problem as being caused by the source column headers; all of which had multiple # at the end.

For example, as you can see in the above error message, DATE was displaying as DATE#######.

We went through the source removing all of the # symbols and were then able to run the integration without receiving more errors.

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