Exchange Rates inserted by eConnect integrations

Microsoft Dynamics GPI recently assisted with a support call logged by a client following the introduction of an RM integration created using SmartConnect.

The client enters exchange rates at the start of the month, but following the integration being deployed, extra exchange rates were being inserted into the exchange rate table. This caused problems as the rate from the external system varied more often than the rates entered, and required, in Microsoft Dynamics GP.

The investigation started from the integration to see if there were any settings in it which could be causing this issue, but none seemed relevant. The only currency fields being set was the Currency ID and the Exchange Rate.

After this I started taking a look into the eConnect stored procedures on top of which SmartConnect runs. After digging down a couple of levels I discovered that taMCExchangeRate has a section which inserts the exchange rate passed in if it is not in the Exchange Rate table; this is regardless of the setting in Multicurrency Setup (Financial area page » Setup » Multicurrency) which were set to allow rates to be used without being added to the exchange rate table.

The client was running Microsoft Dynamics GP 2013 SP2 and my investigation was confirmed on a 2019 October Release environment so this is a long standing issue which is not yet resolved; I have confirmed with Microsoft that they are aware of this issue and it is logged with the development team for resolution in a future version.

In the meantime, I have deployed customised versions of two stored procedures to the client so that they do not have the exchange rates being inserted into the exchange rate table.

SmartConnect Error: Data source name not found…

Microsoft Dynamics GPI’ve recently been working on a SmartConnect project with a client. Integrations were created, tested and signed off as working by the members of the project team. However, when additional users starting using SmartConnect, an error was encountered by some users, not all, running the integrations:

Error running integration

Connection could not be validated

ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

The integrations were using an Excel file data source and, when checked, the users having problems had the 64-bit version of Microsoft Office installed and the working ones had the 32-bit version. You don’t need to repalce the whole office installation, just install the 32-bit version of the Microsoft Access Database Engine 2016 Redistributable from the command line as a silent install.

Using Node Builder to Create New Node: Conclusion

eOne SolutionsThis post is part of the series on Using Node Builder to Create New Node; in particular I m creating a node to add EFT Bank information when adding a creditor.

In this series, I’ve gone through the steps to create a simple node to add EFT Bank details when using SmartConnect to insert a vendor. Node Builder allowed us to create the node without writing any code.

Node Builder is the least polished of the eOne products; in fact, based on how good SmartList Builder and SmartConnect are, I was very surprised at the lack of polish.

The alternative to using Node Bulder is to write your own eConnect stored procedures. Microsoft has posted some example code of how to do this. In addition, Tim Wappat has also posted about this.

If I was creating the node, I’d be tempted to just write my own (as I have done in the past), but when working with a client I would show them Node Builder and explain the pros and cons (including limitations such as not integrating with SmartConnect any more).

Using Node Builder to Create New Node: Add SmartConnect Node

eOne SolutionsThis post is part of the series on Using Node Builder to Create New Node; in particular I m creating a node to add EFT Bank information when adding a creditor.

Once the GP Resource Cache refreshed, the new node will be available in SmartConnect.

To use the node, launch SmartConnect and on the action pane, under GP Connector, click Node Maintenance:

SmartConnect action pane

Continue reading “Using Node Builder to Create New Node: Add SmartConnect Node”

Using Node Builder to Create New Node: Update SmartConnect GP Resource Cache

eOne SolutionsThis post is part of the series on Using Node Builder to Create New Node; in particular I m creating a node to add EFT Bank information when adding a creditor.

With the node created, we need to make it available for use in SmartConnect before we can actually use it.

This is done by refreshing the SmartConnect GP Resource Cache. Do this by launching Microsoft Dynamics GP and selecting GP Resource Cache from the (Microsoft Dynamics GP » Tools » SmartConnect » GP Resource Cache) menu:

GP Resource Cache menu

Continue reading “Using Node Builder to Create New Node: Update SmartConnect GP Resource Cache”

Using Node Builder to Create New Node: Create Node

eOne SolutionsThis post is part of the series on Using Node Builder to Create New Node; in particular I m creating a node to add EFT Bank information when adding a creditor.

To create new node, launch Node Builder from the Windows Start menu.

It will start showing a blank screen. In the General Options pane enter the following:

  • Node ID which is all caps with no spaces
  • Node Description
  • Default Company
  • eConnect Procedure Name which will default in, but can be changed (you can;t change the prefix from E1_
  • Create SmartConnect Node which must be left unmarked
Node Builder 2011: Create new VENRODEFT Node
exclamation 

The Create SmartConnect Node must be left unmarked, even if you want to create a node in SmartConnect. This did work in the past, but development of SmartConnect has continued whle that of Node Builder has stalled.

You will have problems if you mark this box!

In the right pane, select the companies in which the node should be made available.

Continue reading “Using Node Builder to Create New Node: Create Node”

Using Node Builder to Create New Node: Introduction

eOne SolutionsA few weeks ago I did a series on Implementing Node Builder; in this new series I am going to cover creating a new node for adding EFT Bank information with a creditor.

If you’re reading this on azurecurve, the series index, below, will automatically update; if you’re reading a syndicated post, then you’ll need to check back on the original post.

Using Node Builder to Create New Node
Create Node
Update SmartConnect GP Resource Cache
Add SmartConnect Node
Conclusion

Implementing Node Builder: Conclusion

eOne SolutionsThis post is part of the series on Implementing Node Builder; Node Builder is a product which allows additional eConnect nodes to be easily created for use with SmartConnect.

I was somewhat surprised that the most recent version available was the 2011 version; I think this shows that Node Builder is not a very popular product, but I am slightly surprised by this as SmartConnect seems to be a popular choice for integrations. I have manually written eConnect stored procedures for new nodes and Node Builder is an easier and quicker way of creating the nodes.

I assume though that people are generally either creating the stored procedures manually or are doing direct updates to the database. If this is the case, then it would seem that the people mainly using SmartConnect are more technical users.

It does not need to be this way and, for a lot of the SmartConnect projects I’ve had a hand in delivering, it hasn’t been this way as we have installed and configured SmartConnect and then trained users on creating and maintaining integrations.

Node Builder compliments this approach by allowing non-technical users to create new nodes as required rather than needing a SQL develop with experience of Microsoft Dynamics GP and eConnect.

I’ll do a series in a few weeks on using Node Builder to create a node for use with SmartConnect.

Implementing Node Builder: Connection Issue

eOne SolutionsThis post is part of the series on Implementing Node Builder; in particular I m creating a node to add EFT Bank information when adding a creditor.

The first time I installed Node Builder I received an error when trying to log in:

Connection failed

Connection Failed

A connection error occurred while trying to connect o the Node Builder database. Check the server settings to ensure Node Builder is pointing to the correct server.

Continue reading “Implementing Node Builder: Connection Issue”

Implementing Node Builder: Registration

eOne SolutionsThis post is part of the series on Implementing Node Builder; Node Builder is a product which allows additional eConnect nodes to be easily created for use with SmartConnect.

With Node Builder installed we can now launch and register it. Node Builder will be available via the Windows Start menu. When launched, you will be prompted to enter the SQL Server and a user account to connect with; this is making a connection to the SQL Server so you will either need to use the sa account or another SQL account (which is not a Dynamics GP user).

Connection Information

Continue reading “Implementing Node Builder: Registration”