azurecurve

SmartConnect Error: “The delete permission was denied on the object…”

Tuesday 29th Dec 2020Wednesday 9th Dec 2020 Ian Grieve2 minute read0 comment

A while back a client using SmartConnect reported an error running one integration; this is one of a set of newly created identical integrations running against a set of companies, but only one of them was failing.

The error produced was:

Task xxxx failed. Map run will end reporting failure. The DELETE permission was denied on the object 'xxxx', database 'xxxx', schema 'dbo'

As there was a reference to permssions, I assumed there would be a SQL issue; when looking through database permissions, I found that in one database the user account used by SmartConnect had the db_denydatawriter role membership assigned:

Once this permission was removed, the integration ran successfully.

PrintFriendly Email Linkedin Twitter Facebook

SmartConnect could not find data

Monday 28th Dec 2020Wednesday 9th Dec 2020 Ian Grieve2 minute read2 Comments

I recently created an integration using SmartConnect for a client as I have many times before; however, when I came to test the integration, my source file was totally ignored and the integration returned an error that no file was found.

The integration was using a folder data source with an Excel template; nothing special and something which I have configured many times. I copied the template file into the source folder and tried the integration again and got the same result.

I asked another consultant on the team to take a look with me and neither of us could see a problem; everything looked correct. Then it occurred to me that the extension of the file was .XLSX which I would not expect to be a problem; but, we couldn’t see anything else, so changed the extension to .xlsx and tried the integration again.

It worked correctly. I didn’t expect the case of the file extension to cause a problem, but is something to definitely bear in mind in the future and to make sure clients are aware.

PrintFriendly Email Linkedin Twitter Facebook

Recent ISC Software Webinar: Prepayments and Accruals

Thursday 3rd Dec 2020Friday 18th Dec 2020 Ian Grieve1 minute read0 comment

In our most recent webinar, we took a look at Prepayments & Accruals in Microsoft Dynamics GP and how both can be processed using standard functionality, before then taking a look at some of the ways in which accruals can be automated. If you want to catch up on this, or any other, webinar, you can do so here.

There are three main parts to the webinar (plus the references):

Prepayments
Accruals
Automating Accruals
Add-ons referenced in the webinar

Continue reading “Recent ISC Software Webinar: Prepayments and Accruals”

PrintFriendly Email Linkedin Twitter Facebook

Exchange Rates inserted by eConnect integrations

Thursday 2nd Jul 2020Thursday 2nd Jul 2020 Ian Grieve3 minute read2 Comments

I 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.

PrintFriendly Email Linkedin Twitter Facebook

SmartConnect Error: Data source name not found…

Friday 8th May 2020Thursday 13th Jan 2022 Ian Grieve2 minute read1 Comment

I’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:

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 replace 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.

PrintFriendly Email Linkedin Twitter Facebook

Using Node Builder to Create New Node: Conclusion

Friday 23rd Aug 2019Saturday 17th Aug 2019 Ian Grieve2 minute read0 comment

This 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).

Click to show/hide the Using Node Builder to Create New Node Series Index

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

PrintFriendly Email Linkedin Twitter Facebook

Using Node Builder to Create New Node: Add SmartConnect Node

Thursday 22nd Aug 2019Sunday 3rd Nov 2019 Ian Grieve1 minute read0 comment

This 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:

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

PrintFriendly Email Linkedin Twitter Facebook

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

Wednesday 21st Aug 2019Sunday 3rd Nov 2019 Ian Grieve2 minute read0 comment

This 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:

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

PrintFriendly Email Linkedin Twitter Facebook

Using Node Builder to Create New Node: Create Node

Tuesday 20th Aug 2019Saturday 17th Aug 2019 Ian Grieve2 minute read0 comment

This 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

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”

PrintFriendly Email Linkedin Twitter Facebook

Using Node Builder to Create New Node: Introduction

Monday 19th Aug 2019Saturday 17th Aug 2019 Ian Grieve1 minute read1 Comment

A 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.