Getting on towards two years ago, I did a post where I mentioned that AD Groups used as approvers need to have a display name set; I don’t seem to have mentioned that ordinary domain user accounts set as approvers also need to have a display name set.
I’ve recently been reminded about this on a test system where the admin account I was logging in as did not have a display name.
Where there is no display name, you can set the approver, but when you click OK, the name disappears.
This post is part of the series on Implementing SmartConnect, an integration tool from eOne Solutions, which can take data from any source and integrate it into Microsoft Dynamics GP (and other systems such as Microsoft Dynamics CRM or Sales Force amongst others). It has a drag and drop interface to make creating integrations quick and easy for all users rather than just developers (as many integration tools target).
Once the core of SmartConnect has been installed, there are a few steps which need to be completed. The first of these is to configure the eOne SmartConnect Service to start with Windows. In theory it is configured to do so during the installation, but I’ve found that the service tries to start before SQL Server, but fails. This service needs to be running to allow maps to be scheduled to run automatically.
To remedy this problem, you have two options:
Either one of these options, should be sufficient to remedy the issue and allow the service to correctly start and therefore allow maps to be scheduled.