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: Deploy Sample Company

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 system database deployed, the next step is to deploy the Fabrikam, Inc. sample company.

To do this, launch GP Utilities and log in using the sa account:

Welcome to Microsoft Dynamics GP Utilities

Continue reading “Hands On With MDGP 2018 RTM: Deploy Sample Company”

Copy Posting Report Configuration Between Companies

Microsoft Dynamics GPI wrote the first version of this script a long time ago, but recently had cause to return to it. A client I am working with has configured the posting reports in one company and wanted to copy the same configuration to the other companies.

This script allows you to do this, on a one by one basis. Set the first highlighted parameter to the source company, and the second to the destination company.

/*
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).
*/
DECLARE @SQLStatement VARCHAR(8000)
DECLARE @SourceCompany VARCHAR(5) = 'T16R2'
DECLARE @DestinationCompany VARCHAR(5) = 'P16R2'

SET @SQLStatement = 'UPDATE
				['Destination Posting Journal Destinations']
			SET
				PRNTJRNL = ['Source Posting Journal Destinations'].PRNTJRNL
				,ASECTMNT = ['Source Posting Journal Destinations'].ASECTMNT
				,PRTOPRNT = ['Source Posting Journal Destinations'].PRTOPRNT
				,PRTOFLNT = ['Source Posting Journal Destinations'].PRTOFLNT
			FROM
				' + @DestinationCompany + '.dbo.SY02200 AS ['Destination Posting Journal Destinations']
			INNER JOIN
				' + @SourceCompany + '.dbo.SY02200 AS ['Source Posting Journal Destinations'] ON ['Source Posting Journal Destinations'].SERIES = ['Destination Posting Journal Destinations'].SERIES
					AND ['Source Posting Journal Destinations'].TRXSOURC = ['Destination Posting Journal Destinations'].TRXSOURC
					AND ['Source Posting Journal Destinations'].PTGRPTNM = ['Destination Posting Journal Destinations'].PTGRPTNM'
EXEC (@SQLStatement)

As always with an SQL script, please make sure you have a good backup before running it.

Copy Workflow Doesn’t Copy Notification Settings

Microsoft Dynamics GPI made a discovery the other day about the Copy Workflow functionality in Workflow Maintenance (Administration area page >> Setup >> Company >> Workflow >> Workflow Maintenance). I have been working with a client to create a new Purchase Order Processing workflow. After the client did UAT on a test system, we needed to transfer the workflow to the live system.

We did this by copying the Workflow from the test company to the live one using the Coopy functionality. After the copy, users did a little testing on live and found that originators were not receiving notifications, but users were receiving the task assignment emails.

This was not the first email issues we had encountered during the project, but turned out to be the simplest to resolve (although it took longer than it should to identify).

To correct the issue, open the Workflow and click the expansion arrow next to the Send notifications for completed actions checkbox and remark the checkboxes for the notifications which should be sent:

Workflow Email Notification Maintenance

Workflow 2.0 Requires Display Names for AD Groups Used as Approver

Microsoft Dynamics GPMicrosoft Dynamics GP supports the use of both Active Directory Groups and Users as approvers, but there is a minor catch in the creation of groups which it is easy to stumble over. If you create the group as usual via the Active Directory Users and Computers applet you set a Group name and Group name (pre-Windows 2000):

Active Directory Users and Computers - New Object Group

Continue reading “Workflow 2.0 Requires Display Names for AD Groups Used as Approver”

How To Install Microsoft SQL Server 2016: SSIS Configuration For Named Instances

Microsoft Dynamics GPThis is a short series of posts on how to install Microsoft SQL Server 2016; the series index can be found here.

In the last post, I installed SSIS, but if you are using a named Instance of SQL Server, there is a configuration step required.

To make the change, there is a file called MsDtsSrvr.ini which, for SQL Server 2016, is located in C:\Program Files\Microsoft SQL Server\130\DTS\Binn. The ServerName needs to be changed to include the full SQL Server Instance Name (as highlighted below):

MsDtsSrvr.ini file in Notepad

Once the full SQL Server Instance Name was added and the file saved, SSIS is ready to use.

Click to show/hide the How To Install Microsoft SQL Server 2016 Series Index

How To Install Microsoft SQL Server 2016: Configuring SQL Server Reporting Services

Microsoft Dynamics GPThis is a short series of posts on how to install Microsoft SQL Server 2016; the series index can be found here.

In the last post, I installed the SQL Server Database Engine and the Reporting Services, but I did not configure Reporting Services. I mentioned that I have had problems before when doing this, so always do it separately.

To configure SQL Server Reporting Services (SSRS), launch Reporting Services Configuration Manager from the Windows Start menu.

Select the Report Server Instance to connect to and click Connect:

Reporting Services Configuration Connection

Continue reading “How To Install Microsoft SQL Server 2016: Configuring SQL Server Reporting Services”

How To Install Microsoft SQL Server 2016: Series Index

Microsoft Dynamics GPA new version of SQL Server came out last year, and I’ve been creating some new demo machines for use at work. It has become habit to screenshot everything I install or configure, so I decided I might as well post a small series on how to install Microsoft SQL Server 2016 and it’s component parts.

The posts will be made over the coming days and show in the series index, below:

How To Install Microsoft SQL Server 2016
Installing SQL Server Database Engine
Configuring SQL Server Reporting Services
Installing SQL Server Analysis Services
Installing SQL Server Integration Services
SSIS Configuration For Named Instances
Installing SQL Server Management Studio

The installation of SQL Server has been broken down into different posts, as I don’t install all components all of the time, but only install the ones which are required at the time.