After assisting a client with a server migration, an issue was reported with a fixed asset integration:
DOC 1 ERROR: The stored procedure 'taCreateAssetID' doesn't exist.
The first thing we checked was to see if the stored procedure did exist, which it did. The next option was a suspicion of permissions. After checking in SQL I found that the service account did not have access to all of the company databases; we added the DYNGRP database role to the service account and tried the integration again and found that it now ran successfully.
In the last post, I covered installing the eConnect Runtime on a client which makes it available to Integration Manager. In this post, I am going to install Integration Manager with both the standard and eConnect adaptors.
Launch the Dynamics GP Setup Utility and under Additional Products select Integration Manager. Accept the terms of the License Agreement and click Next:
I helped a client create a bank transaction integration in Integration Manager the other day. It’s been a while since I created an integration like this, so we created it as I would a general ledger integration with a header and distribution file with two distributions for each transaction. However, when we ran the integration, we received this error message:
This integration was only for creating increase adjustment transactions, so we amended the integration so that only the Debit Amount destination field was mapped. After making this change, the integration ran successfully.
Integration Manager installs with a sample database in the install folders as the default database. In virtually every case, the clients I work with have a centralised database shared by all clients. While users can amend the path through the Integration Manager application, you can also add a setting in the Microsoft.Dynamics.GP.IntegrationManager.ini file (by default located in C:\Program Files (x86)\Microsoft Dynamics\Integration Manager 18) to change the location for all users.
Under the [IMBaseProvider] heading add the following line where the highlighted section is the path to the database:
In our most recent webinar, we took a look at Automation in Microsoft Dynamics GP. In this webinar, we covered how automation can be used in Microsoft Dynamics GP to improve efficiencies and accuracy of data. If you want to catch up on this, or any other, webinar, you can do so here.
In this blog post, I am going to recap the webinar and cover the highlights of how automation can be used in Microsoft Dynamics GP to improve efficiencies and improve data accuracy:
Where possible in this webinar I highlighted standard, or Microsoft supplied, features or additional products where they are available. However, in many cases the standard functionality does not allow for full automation. This is an intentional design choice made when Microsoft Dynamics GP was first created back in the md-90s. The company who created Great Plains, the original name of Dynamics GP, was intended from the very beginning to be extensible with the intention that there be a thriving third-party marketplace for add-ons.
This is the current situation; the core Dynamics GP system has strong core financials and distribution modules, but wider functionality is provided by third party (Independent Software Vendors (ISVs) who have a variety of add-ons and complimentary products which provide the functionality required or automating processes. In each of the areas, there are usually a number of products available from several vendors, but I have selected one in each area. usually an add-on which I have used with several clients across a number of years and which has received positive reviews.
Before implementing one of the solutions, I’d recommend reviewing the functionality it includes, the functionality of competing products and making your own decision about which will best fit your requirements.
Once Integration Manager has been installed, we can run it for the first time. When launching it for the first time, make sure you do so using right click and Run as Administrator to make sure it has the elevated permissions necessary to create the required registry changes.
Integration Manager is a commonly used integration tool which can be used to import card and transaction data into Microsoft Dynamics GP. One of the, optional, prerequisites for Integration Manager is eConnect; eConnect provides a second set of adaptors for integrating data through Integration Manager.
Launch the setup utility and, under the Additional Products heading, select Integration Manager:
I created an integration recently using Integration Manager for a client to import sales invoices into Microsoft Dynamics GP. It worked fine when I was developing it, logged in as DYNSA, and for one of the finance teams managers, but produced an error for the user:
Opening source query...
Establishing source record count...
DOC 1 ERROR: Unknown Great Plains field subtype '10016'. - Field 'Deposit Received' of window 'SOP_Entry' of form 'SOP_Entry'
DOC 2 ERROR: Unknown Great Plains field subtype '10016'. - Field 'Deposit Received' of window 'SOP_Entry' of form 'SOP_Entry'
DOC 3 ERROR: Unknown Great Plains field subtype '10016'. - Field 'Deposit Received' of window 'SOP_Entry' of form 'SOP_Entry'
DOC 4 ERROR: Unknown Great Plains field subtype '10016'. - Field 'Deposit Received' of window 'SOP_Entry' of form 'SOP_Entry'
DOC 5 ERROR: Unknown Great Plains field subtype '10016'. - Field 'Deposit Received' of window 'SOP_Entry' of form 'SOP_Entry'
DOC 6 ERROR: Unknown Great Plains field subtype '10016'. - Field 'Deposit Received' of window 'SOP_Entry' of form 'SOP_Entry'
DOC 7 ERROR: Unknown Great Plains field subtype '10016'. - Field 'Deposit Received' of window 'SOP_Entry' of form 'SOP_Entry'
7 documents were read from the source query.
7 documents were attempted:
0 integrated without warnings.
0 integrated with warnings.
7 failed to integrate.
I toggled the Integration Manager ini file parameters so I could see what was happening with the windows to get an indication of the problem. The first window opened was Sales Order Processing Setup; why tis opened I’m not sure, but the user didn’t have permissions for this window. I did a quick test by copying the users security to a test account and added access to that window and the integration ran through without a problem.
This seems to be an operating as designed thing, but it seems odd that the SOP Setup window needs access.
I’ve recently been working with a client to implement Microsoft Dynamics GP and have been using Integration Manager to import the opening data. While importing payables transactions I encountered the following error:
The vendor has an existing purchase order. Choose Continue to post or save. Choose Go To to view a purchasing navigation list. Choose Cancel to return to the window...