Feature Explained: Invoice Receipt Date

Microsoft Dynamics GPBack in 2017, regulations in the UK changed so that business of a certain minimum size, had to start recording the date an invoice was received. To support this new regulation, Microsoft introduced a new Invoice Receipt Date field to a number of windows in the Purchasing series. This new field was introduced in the July 2017 hotfix.

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 (Purchasing area page » Transactions » Transaction Entry)
  • Receivings Transaction Entry (Purchasing area page » Transactions » Receivings Transaction Entry)
  • Purchasing Invoice Entry (Purchasing area page » Transactions » Enter/Match Invoice)

Taking Payables Transaction Entry as an example, to access the Payables Date Entry field, click the expansion arrow next to the Doc. Date field:

Payables Transaction Entry

Continue reading “Feature Explained: Invoice Receipt Date”

Create SmartConnect Journal – Standard Map: Conclusion

eOne SolutionsThis post is part of a series on creating a Journal – Standard integration using SmartConnect from eOne Solutions; I recently posted a series on Implementing SmartConnect.

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.

Create SmartConnect Journal – Standard Map: Could Not Run The Scheduled Map

eOne SolutionsThis post is part of a series on creating a Journal – Standard integration using SmartConnect from eOne Solutions; I recently posted a series on Implementing SmartConnect.

The final error I received while creating the Journal – Standard map was when I scheduled the map to run automatically:

Windows Event Viewer showing error

JOURNALSTANDARD : SmartConnect Scheduler : Could not run the scheduled map You do not have access to the connectors required for this map.

Continue reading “Create SmartConnect Journal – Standard Map: Could Not Run The Scheduled Map”

Create SmartConnect Journal – Standard Map: Credit Amount Was Not Supplied Error

eOne SolutionsThis post is part of a series on creating a Journal – Standard integration using SmartConnect from eOne Solutions; I recently posted a series on Implementing SmartConnect.

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:

SmartConnect Progess window showing error

Continue reading “Create SmartConnect Journal – Standard Map: Credit Amount Was Not Supplied Error”

Create SmartConnect Journal – Standard Map: Connection Could Not be Validated Error

eOne SolutionsThis post is part of a series on creating a Journal – Standard integration using SmartConnect from eOne Solutions; I recently posted a series on Implementing SmartConnect.

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

SmartConnect

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.

Create SmartConnect Journal – Standard Map: Schedule Integration

eOne SolutionsThis post is part of a series on creating a Journal – Standard integration using SmartConnect from eOne Solutions; I recently posted a series on Implementing SmartConnect.

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.

Map Setup action pane with Schedule button

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:

Schedule window showing new schedule

Click Save to save the schedule and then click Save again to save the new integration map.

Create SmartConnect Journal – Standard Map: Run Integration

eOne SolutionsThis post is part of a series on creating a Journal – Standard integration using SmartConnect from eOne Solutions; I recently posted a series on Implementing SmartConnect.

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:

SmartConnect Progress window showing map was successful

Continue reading “Create SmartConnect Journal – Standard Map: Run Integration”

Create SmartConnect Journal – Standard Map: Define Header Mapping

eOne SolutionsThis post is part of a series on creating a Journal – Standard integration using SmartConnect from eOne Solutions; I recently posted a series on Implementing SmartConnect.

In the last post, I stepped through mapping of the journal lines; in this post, I’ll cover mapping of the journal header.

From the Map Setup window, double-click on the Create journal line in the scrolling window.

As shown in the image, below, map the BatchID, TrxDate, Reference and JRNENTRY fields from the source to the destination. If JRNENTRY doesn’t show here then you have not marked the Use as Global Variable in the GP Rolling Column window).

You also need to change the Column Type on the Transaction type row to List Option and then set the Column Name to Regular; this will make sure the integrated journal is created as a standard journal.

SmartConnect Mapping window showing mapping of fields

Continue reading “Create SmartConnect Journal – Standard Map: Define Header Mapping”

Create SmartConnect Journal – Standard Map: Configure Distributions

eOne SolutionsThis post is part of a series on creating a Journal – Standard integration using SmartConnect from eOne Solutions; I recently posted a series on Implementing SmartConnect.

With the Destination configuration started, the next step is to define the distribution field mapping.

Double click the Add distribution entry in the scrolling window at the bottom of the Map Setup window when the Destination section is selected:

Map Setup window showing Destination section is selected

Continue reading “Create SmartConnect Journal – Standard Map: Configure Distributions”

Create SmartConnect Journal – Standard Map: Configure Destination

eOne SolutionsThis post is part of a series on creating a Journal – Standard integration using SmartConnect from eOne Solutions; I recently posted a series on Implementing SmartConnect.

With the integration map heading created, the next step is to define the destination.

On the Map Setup window which will still be open from the previous post, click the down chevron button next to the Destination heading.

Set Destination Type to Microsoft Dynamics GP.

In the Settings section, there are two fields to define:

  1. Set Group to General Ledger.
  2. Set Node Type to Transactions.
Map Setup window showing Destination settings

Click the Companies button and select the company the integration is to be run against.

In the next post, I’ll take a look at mapping of the distributions.