Hands On With MDGP 2018 RTM: eConnect Incoming Queue Bug Fixed

Microsoft Dynamics GPMicrosoft Dynamics GP 2018 RTM has now been released. In this series of posts, I will be stepping through the installation of Microsoft Dynamics GP and additional products and then will move on to taking a look at the new functionality which has been introduced.

The series index for this series of posts is here and will automatically update as posts go live.

There was a bug in the Microsoft Dynamics GP 2015 and 2016 versions of eConnect whereby the Integration Service was unable to process messages from the Incoming Queue.

I’ve done some testing of this in eConnect for Microsoft Dynamics GP 2018, and I’m delighted to confirm that the bug has now been fixed. This is great news as it means we will no longer need to be installing the Incoming queue for Microsoft Dynamics GP 2013 R2.

My colleague, Laura Bowie, has also informed me that the year end updates for Microsoft Dynamics GP 2015 and 2016 has also seen this bug fixed.

Click to show/hide the Hands On With MDGP 2018 RTM Series Index

Hands On With MDGP 2018 RTMS: Set eConnect Incoming Queue Permissions

Microsoft Dynamics GPMicrosoft Dynamics GP 2018 RTM has now been released. In this series of posts, I will be stepping through the installation of Microsoft Dynamics GP and additional products and then will move on to taking a look at the new functionality which has been introduced.

The series index for this series of posts is here and will automatically update as posts go live.

With the eConnect Service and the eConnect Incoming Queue configured, the final step is to configure permissions of the queue to accept messages.

Launch Computer Management from the Control Panel on the eConnect server. Expand the following nodes:

  • Services and Applications
  • Message Queuing
  • Private Queues

Right click on econnect_incoming and select Properties

Computer Management

In the Group or users names list, select Everyone and set Permissions for Everyone to Full Control. Click OK to accept the changes

Continue reading “Hands On With MDGP 2018 RTMS: Set eConnect Incoming Queue Permissions”

Hands On With MDGP 2018 RTM: Configure eConnect Incoming Queue

Microsoft Dynamics GPMicrosoft Dynamics GP 2018 RTM has now been released. In this series of posts, I will be stepping through the installation of Microsoft Dynamics GP and additional products and then will move on to taking a look at the new functionality which has been introduced.

The series index for this series of posts is here and will automatically update as posts go live.

With the eConnect Service configured, the next step is to configure the Incoming Queue.

This configuration change is done in the eConnect_Incoming.exe.config file which is located, by default, in C:\Program Files\Microsoft Dynamics\eConnect 18.0\Service\Incoming Service:

Windows Explorer

Continue reading “Hands On With MDGP 2018 RTM: Configure eConnect Incoming Queue”

Hands On With MDGP 2018 RTM: Configure eConnect Service

Microsoft Dynamics GPMicrosoft Dynamics GP 2018 RTM has now been released. In this series of posts, I will be stepping through the installation of Microsoft Dynamics GP and additional products and then will move on to taking a look at the new functionality which has been introduced.

The series index for this series of posts is here and will automatically update as posts go live.

With eConnect installed on the server, there are a couple of pieces of configuration which need to be done. The first is covered in this blog post, and that is the configuration of the eConnect Service.

Perfect Image maintain and support a Dexterity Extension written by a company which is no longer a Microsoft Dynamics partner; this customisation receives transactions via eConnect from an external line of business system. The default configuration results in timeouts if the eConnect service isn’t configured to receive large messages; which basically means adding the following to the Microsoft.Dynamics.GP.eConnect.Service.exe.config file:

receiveTimeout="infinite"

To add this element to the bindings node of the configuration file, open Windows Explorer and navigate to the file in C:\Program Files\Microsoft Dynamics\eConnect 18.0\Service.

Edit the node so it looks like the below and then save the file:

Notepad

Stop and restart the eConnect service to ensure the change is picked up.

Click to show/hide the Hands On With MDGP 2018 RTM Series Index

Hands On With MDGP 2018 RTM: Install eConnect on Server

Microsoft Dynamics GPMicrosoft Dynamics GP 2018 RTM has now been released. In this series of posts, I will be stepping through the installation of Microsoft Dynamics GP and additional products and then will move on to taking a look at the new functionality which has been introduced.

The series index for this series of posts is here and will automatically update as posts go live.

With the eConnect prerequisites configured or installed (as appropriate), eConnect can now be installed on the server. eConnect is installed from the setup.exeRun on each one as it appears:

Click Install on the Microsoft Dynamics GP 2018 Bootstrapper Setup:

Microsoft Dynamics GP 2018 Bootstrapper Setup

Continue reading “Hands On With MDGP 2018 RTM: Install eConnect on Server”

eConnect 18 Prerequisites: Set Service Install MSMQ Triggers

Microsoft Dynamics GPMicrosoft Dynamics GP 2018 RTM has now been released and I am in the middle of a series of Hands On posts. As part of thsat series, I am about to cover the installation of the eConnect additional product on a server configured for receiving messages via the MSMQ. However, there are two prerequisites which need to be dealt with before eConnect can be installed on the server.

Usually, when doing Hands On posts, I only cover the core installs and only mentioned prerequisites such as this, referring back to old posts were necessary, but it appears I’ve only made references previously to what you have to do, without actually blogging about it. So, this series on the eConnect prerequisites, is going to be a brief diversion from the Hands On series, which will resume tomorrow.

The eConnect 18 Prerequisites series index can be found here.

Before eConnect can be installed and configured to receive messages from the Microsoft Message Queue, the Message Queuing Triggers need to be installed. This is done via Server Manager:

Click Add roles and features link:

Server Manager

Continue reading “eConnect 18 Prerequisites: Set Service Install MSMQ Triggers”

eConnect 18 Prerequisites: Set Service Account as Local Administrator

Microsoft Dynamics GPMicrosoft Dynamics GP 2018 RTM has now been released and I am in the middle of a series of Hands On posts. As part of thsat series, I am about to cover the installation of the eConnect additional product on a server configured for receiving messages via the MSMQ. However, there are two prerequisites which need to be dealt with before eConnect can be installed on the server.

Usually, when doing Hands On posts, I only cover the core installs and only mentioned prerequisites such as this, referring back to old posts were necessary, but it appears I’ve only made references previously to what you have to do, without actually blogging about it. So, this series on the eConnect prerequisites, is going to be a brief diversion from the Hands On series, which will resume tomorrow.

The eConnect 18 Prerequisites series index can be found here.

Before installing eConnect, the service account it will run under needs to be configured as a local administrator. Do this by launching the Computer Management Control Panel applet.

Expand the following nodes in the navigation tree:

  1. System Tools
  2. Local Users and Groups
  3. Groups

Double click on the Administrators group in the central list of groups:

Computer Management - System Tools  - Local Users and Groups - Groups

Continue reading “eConnect 18 Prerequisites: Set Service Account as Local Administrator”

eConnect 18 Prerequisites: Series Index

Microsoft Dynamics GPMicrosoft Dynamics GP 2018 RTM has now been released and I am in the middle of a series of Hands On posts.

As part of that series, I am about to cover the installation of the eConnect additional product on a server configured for receiving messages via the MSMQ. However, there are two prerequisites which need to be dealt with before eConnect can be installed on the server.

Usually, when doing Hands On posts, I only cover the core installs and only mentioned prerequisites such as this, referring back to old posts were necessary, but it appears I’ve only made references previously to what you have to do, without actually blogging about it.

So, this series on the eConnect prerequisites, is going to be a brief diversion from the Hands On series, which will resume tomorrow.

eConnect 18 Prerequisites
Set Service Account as Local Administrator
Set Service Install MSMQ Triggers

Hands On With MDGP 2018 RTM: Install eConnect on Client

Microsoft Dynamics GPMicrosoft Dynamics GP 2018 RTM has now been released. In this series of posts, I will be stepping through the installation of Microsoft Dynamics GP and additional products and then will move on to taking a look at the new functionality which has been introduced.

The series index for this series of posts is here and will automatically update as posts go live.

A number of my clients use Integration Manager for loading data into Microsoft Dynamics GP; a number of the integrations are either available only with, or run faster with, the eConnect adaptor. So before Integration Manager itself can be installed, eConnect needs to be installed on the client machine.

eConnect is available through the setup utility under the Additional Products header. Before you get to select this though, you may need to click through some security warnings.

Depending on server settings, you might receive multiple security warnings during the installation; click Run on each one as it appears:

Setup Utility

Continue reading “Hands On With MDGP 2018 RTM: Install eConnect on Client”

Stored Procedure To Get Next Purchase Receipt Number

Microsoft Dynamics GPThis stored procedure can be executed to generate the next sequential purchase receipt number which can be used for both receivings transactions (Shipment and Shipment/Invoice) and invoices; the generated invoice was then added to the integration file which was then submitted to eConnect. I’ve written this stored procedure at least three times for different integrations, so thought it best to post it here so I don’t write it again.

-- drop stored proc if it exists
IF OBJECT_ID (N'usp_AZRCRV_GetNextPOPReceiptNumber', N'P') IS NOT NULL
    DROP PROCEDURE usp_AZRCRV_GetNextPOPReceiptNumber
GO
-- create stored proc
CREATE PROCEDURE usp_AZRCRV_GetNextPOPReceiptNumber AS
/*
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).
*/
BEGIN
	DECLARE @return_value INT
	DECLARE @I_vInc_Dec TINYINT = 1
	DECLARE @O_vPOPRCTNM AS VARCHAR(17)
	DECLARE @O_iErrorState INT

	exec @return_value = taGetPurchReceiptNextNumber  @I_vInc_Dec, @O_vPOPRCTNM = @O_vPOPRCTNM OUTPUT,  @O_iErrorState = @O_iErrorState OUTPUT
	SELECT @O_vPOPRCTNM
END
GO

-- grant execute permission on stored proc to DYNGRP
GRANT EXECUTE ON usp_AZRCRV_GetNextPOPReceiptNumber TO DYNGRP
GO

-- execute stored proc
EXEC usp_AZRCRV_GetNextPOPReceiptNumber
GO

The stored proc calls a Microsoft Dynamics GP stored procedure which actually does the work, so we are still getting the receipt number using standard functionality.