The first financial enhancement is the addition of a Long Description field, allowing up to 200 characters, to payables transactions. The new long description needs to be enabled before it can be used. To enable the new field, open Payables Management Setup () and mark the Enable Long Description in Payables Transaction Entry:
Microsoft Dynamics GP
A get/change first operation failed on table 'IV_TRX_WORK_LINE' failed accessing SQL data.
The presence of this field does not seem especially well-known, so I figured I do a quick post covering where it is and how it would be used.
The Invoice Receipt Date has been added to the Date Entry windows for the three types of transaction:
- Payables Transaction Entry ( )
- Receivings Transaction Entry ( )
- Purchasing Invoice Entry ( )
Taking Payables Transaction Entry as an example, to access the Payables Date Entry field, click the expansion arrow next to the Doc. Date field:
Over the last few posts in this series, I have shown how to create a simple General Journal integration.
The process is slightly more involved than creating a similar integration, but the huge advantage is being able to schedule the integration to automatically run and select all files from a folder.
With Integration Manager, to allow multiple people to use the same integration you had to point it at a shared drive letter which all users had in common (and often not all did, due to being in different locations).
In addition, SmartConnect can also process the Excel spreadsheet directly, without requiring the user to save the active page down as a CSV; something which Excel really doesn’t want you to do.
The other main benefit of SmartConnect is that if there is an eConnect node available, it can integrate that type of record into Microsoft Dynamics GP, whereas Integration Manager could only use the ones available via the standard or eConnect adapters.
eOne Solutions also have a product called Node Builder which allows additional eConnect nodes to easily be created without the need for a developer. I’ll be taking a look at NodeBuilder in a future series.
The final error I received while creating the Journal – Standard map was when I scheduled the map to run automatically:
JOURNALSTANDARD : SmartConnect Scheduler : Could not run the scheduled map You do not have access to the connectors required for this map.
While I was creating the Journal – Standard for this series, it was not all smooth sailing. I received an error message while testing the integration:
When I was creating the Journal – Standard for a client recently, I encountered a problem when trying to add a Key Field in the Map Setup window:
Connection could not be validated
ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
This integration polls for Excel spreadsheets in a certain folder; it took me a moment to realise that the server I was working on was a new one and did not have Microsoft Excel installed.
I asked the client of they could install it for me and, once they had done so, the error disappeared and I was able to add the key fields without further problems.
Before creating the schedule, select the Options tab and mark the Allow any user to run this map checkbox. This will allow the service account to run this map on the schedule once it is created.
The journal standard integration is one which I would usually schedule to run periodically throughout the day. This is done as the final step in creating the integration from the Map Setup window by clicking Schedule on the toolbar.
The Schedule window will popup and allow you to configure the schedule as required:
Click Save to save the schedule and then click Save again to save the new integration map.
Over the last few posts, I’ve stepped through the creation of a map in SmartConnect; with the map now completed, it is time to test.
To do this click the Run button on the Map Setup window.
A SmartConnect Progress window will be displayed and show the progress; as you can see below, my source file with one journal in has been successful: