This post is part of the Features of SalesHQ from ISC Software, as well as part of the over-arching GP Elementz from ISC Software series.
Earlier today I published an introduction to SalesHQ post, but I am experimenting with making video alternatives to the standard blog posts.
You can watch the GP Elementz – SalesHQ – Introduction to SalesHQ video:
This post is part of the Features of SalesHQ from ISC Software, as well as part of the over-arching GP Elementz from ISC Software series.
SalesHQ allows you to provide customers with self-serve access to their Microsoft Dynamics GP receivables account data such as invoices, statements and transaction reports. This access is available from anywhere, on any device, in real-time.
Internal salespeople can also be given access to their assigned customers giving access to all of the above; multiple salespeople can be assigned to the same clients (allowing managers to see all of their team’s customers).
Salespeople can also create prospects, raise quotes, orders and invoices as well run SSRS reports.
SalesHQ is a safe and secure cloud based business portal which is also simple and easy to use. It can be branded using your own company logo and/or image so users know they are in the right place.
This post is part of the Features of SalesHQ from ISC Software, as well as part of the over-arching GP Elementz from ISC Software series.This post is part of the GP Elementz from ISC Software series, but is also the series index for the Features of SalesHQ from ISC Software sub-series.
In this series of posts I am going to take a look at the features of the SalesHQ portal.
If you’re reading direct on azurecurve, the series index will automatically update, otherwise, you’ll need to check the original post to see the new posts.
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.
In the last post, I mentioned moving an SSL certificte between stores and thought it might be worth showing how to do it.
Launch the Microsoft Management Console (Win+R and type mmc) and click the File menu and select Add/Remove Snap-in…:
Continue reading “Move SSL certificate to a different store”
With the current situation a lot of clients now have people working from home using a number of approaches. One of them is to use the Workflow module for document approvals and the integration with Web Services for approval via email. When approvals are done by email on devices outside the domain, the web services need to be securely configured with an SSL certificate.
I was recently working on a Workflow project for a client, but ran into an error when adding the SSL certificate to the web services. When I ran the netsh http add sslcert, I received this error:
SSL Certificate add failed, Error: 1312
A specified logon session does not exist. It may already have been terminated.
I’ve not seen this error before, so some investigation was in order. As part of the project, I had provided pre-requisites to the client who had forwarded them into their IT partner to sort out. I discovered that when they added the SSL certificate they had, perhaps not unreasonably, added it to the WebHosting certificate store, but it needed to be in the Personal store.
Once the certificate had been moved, I was able to add the certificate to web services and continue with the configuration.
One item I did flag to the client, is that people wanting to do an approval on a mobile (cell) phone, is that it will not work on Android Chrome as this has retired TLS 1.0 and all of the main browsers will be following suite very soon. While I expect Microsoft to provide a fix for this, an upgrade of Microsoft Dynamics GP will most likely be required.
The client is keeping this under review and may opt to purchase the PurchaseHQ GP Elementz Portal from ISC Software which allows for secure access via an Azurehosted portal with full Microsoft Dynamics GP Workflow integration for document approvals of all Purchasing series workflows.
In a post a couple of weeks ago on emailing from Microsoft Dynamics GP, I mentioned using Office365 Exchange integrationfor sending the emails. Usually this works fine, but, increasingly, clients are activating 2FA (Two-factor authentication) is being enabled, which means users cannot log on using their normal password as the Microsoft Dynamics GP doesn’t use 2FA.
You can however create an app password in Office365 which you can use to log in when emailing documents from Microsoft Dynamics GP.
To create an app password, log into your Office365 account and select My account by clicking on your avatar in the top right corner.
The on the left-hand navigation pane select Security & privacy and then, on the right, click Additional security verification:
Continue reading “Creating an Office365 app password for emailing with Microsoft Dynamics GP”
With more clients working remotely, there has been an increase in the number of people asking me about Microsoft Dynamics GP not scaling text properly. The problem can occur in the text showing either very small or very large (with different versions of Microsoft Dynamics GP handling fonts differently they can display with different problems):
This issue has been raised with me by users with the issue on local clients running on high DPI devices like the Microsoft Surface or when using them to access Microsoft Dynamics GP via RDP.
Fortunately, there is a known workaround available for this issue. Steve Endow on his old Dynamics GP Land blog post about resolving the issue using a manifest file. Then in 2018, Nathan Hayden posted about a similar approach for remote desktop connections.
The first step is to create a manifest file called Dynamics.exe.manifest or Mstsc.exe.manifest (depending on whether you’re fixing the issue for a local or remote desktop accessed client) containing this XML:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3">
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="*" publicKeyToken="6595b64144ccf1df" language="*">
</assemblyIdentity>
</dependentAssembly>
</dependency>
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.VC90.CRT" version="9.0.21022.8" processorArchitecture="amd64" publicKeyToken="1fc8b3b9a1e18e3b">
</assemblyIdentity>
</dependentAssembly>
</dependency>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel level="asInvoker" uiAccess="false"/>
</requestedPrivileges>
</security>
</trustInfo>
<asmv3:application>
<asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
<ms_windowsSettings:dpiAware xmlns:ms_windowsSettings="http://schemas.microsoft.com/SMI/2005/WindowsSettings">false</ms_windowsSettings:dpiAware>
</asmv3:windowsSettings>
</asmv3:application>
</assembly>
This file should be placed next to the exe file to which it should be applied. By default, this will be %ProgramFiles(x86)%\Microsoft Dynamics\GP (adjust based on your version or install folder) or %windir%\SysWOW64\ depending on if the fix is for a local or remote desktop accessed client.
Then use the below to create a manifest.reg file to add the DWord registry entry which tells Windows to prefer and use the external manifest just created:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide]
"PreferExternalManifest"=dword:00000001
Once you’ve created the registry file above, double-click it to add the DWord to the registry.
When you next launch Microsoft Dynamics GP or connect to the RDP session and launch it, the text in the client should display correctly.
A few years ago I used to have a Windows desktop covered in icons, which was almost a throwback to the old Windows 3 Program Manager (I think that’s what it was called, but I had to look it up). In recent years, I’ve tended to go for a much cleaner look to the desktop and use a lot of shortcuts to start applications instead.
I dislike having the Recycle Bin on the desktop, which is there by default, but because Microsoft have been shuffling settings around a lot, I never remember where the setting is to turn it off, so this post is a reminder.
To switch off (or on) the desktop icons, launch the Themes Settings applet by right-clicking the desktop and select Personalise (or launch it using the ms-settings:themes URi).
When launched, select Desktop icon settings on the right (or at the bottom if the window is narrow):
This post is part of the Features of CustomerHQ from ISC Software, as well as part of the over-arching GP Elementz from ISC Software series.
Earlier today I published a Free Trial available post, but I am experimenting with making video alternatives to the standard blog posts.
You can watch the GP Elementz – CustomerHQ – Free Trial Available video: