After installing the Microsoft Dynamics GP client component, you need to run Microsoft Dynamics GP as administrator as you will be prompted to include new code; click Yes to do so:
Once Enhanced Notes has been installed, you need to start Microsoft Dynamics GP as an administrator as new code needs to be included:
This post is part of the series on Implementing SmartConnect, an integration tool from eOne Solutions, which can take data from any source and integrate it into Microsoft Dynamics GP (and other systems such as Microsoft Dynamics CRM or Sales Force amongst others). It has a drag and drop interface to make creating integrations quick and easy for all users rather than just developers (as many integration tools target).
The next step in installing SmartConnect, is to install the GP Addin. This was in the zip we downloaded as part of the installation post; launch the SmartConnect GP Addin….exe.
Select the relevant version of Microsoft Dynamics GP from the list and click Next:
This post is part of a series of posts on Implementing Rockton’s SmartFill.
The first step in implementing SmartFill is to install the first client; it’s in this installation where we will deploy the database objects.
To install the first client, the first step is to download SmartFill; navigate to the Rockton Software downloads page. In the Product field, select
SmartFill and in the Versions field select
Microsoft Dynamics GP Version 2018.
Mark the checkbox next to the Product and hit the Download Selected button:
With 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:
Once 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:
Now that Microsoft Dynamics GP 2015 RTM is available, I thought I could follow my usual pattern of posting a series of posts on how to install and configure both Dynamics GP, but also the additional products which ship with it. You can find the series index for these posts here.
The first run of Integration Manager is something needed on each client. When staring Integration Manager for the very first time it is important to Run as Administrator.
When Integration Manager starts for the first time, you will be prompted to Register Now or Register Later; if you choose the latter option, Integration Manager will close:
I was working on a new integration template for a client recently and after accidentally closed Integration Manager instead of just the Destination Mappings window I started getting the below error message when I reopened and tried running the integration:
It took me a few minutes of fiddling around to work out the problem, but when I did it was a bit of a face/palm moment.
The project I was working on had some customisations in Microsoft Dynamics GP as well as a new integration template. When I logged in first thing I had started GP using Run as Administrator and then launched Integration Manager from the Tools menu (); but, when reopening it, I had launched it from the Windows Start screen.
This meant that GP itself was running under the administrator account, but Integration Manager was running under my user account. I closed Integration Manager again and then launched it from the GP menu, so that it was running under the same user account as GP itself, and was able to run the integration without further problems.
After clicking the Run button the following message popped up:
This error is typically one seen when Microsoft Dynamics GP is not running (I’ve seen it at a few clients running Citrix when they have Integration Manager running on one server and Microsoft Dynamics GP on another), but I had Microsoft Dynamics GP open in the background.
I quickly realised the problem; I had imported some modified reports into GP which contained VBA and to avoid an error I had right clicked and used Run as Administrator when starting Microsoft Dynamics GP, but had started Integration Manager normally.
This meant the two applications were running in different states and Integration Manager could not see Microsoft Dynamics GP.
To resolve the issue I closed Integration Manager and reopened it using the menu in Microsoft Dynamics GP (); this is the way I typically recommend clients open it in order to avoid this problem on Citrix XenApp or other ways of publishing applications.