Quadient AP connects to your Dynamics GP using our data synchronization tool, SmartSync. SmartSync allows us to access the data needed so that you accomplish your workflow needs. There are specific installation requirements to ensure this SmartSync integrates seamlessly for you. This document will walk you through the necessary setup required for SmartSync.
General Requirements
System Requirements
Typical Environment | Required .NET Version | Required TLS Version | Min Requirements |
· Windows Server 2012 R2 · Windows Server 2016 · Windows Server 2019 · Windows 10 · Windows 7.8.1 | 4.8 (528372) | 1.2 | 500MB HDD 16GB RAM |
.NET Version requirements
SmartSync requires a .NET version of 4.8 or above to run successfully. To check your .NET version, run Windows Powershell on your server, and then run the following command:
(Get-ItemProperty "HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full").Release.
Verify your six-digit string below to ensure you are on the correct .NET version.
Typical Environment | .NET version 4.8 release DWORD |
Windows 11/Windows Server 2022 | 528449 |
Windows 10 - May 2020 Update/October 2020 Update/May 2021 Update | 528372 |
Windows 10 - May 2019/November 2019 Update | 528040 |
All other OS versions | 528040 |
You must upgrade your server before your Integration meeting if you are not on .NET version 4.8 or higher. The update will require a server restart. Click here to upgrade your .NET version.
Windows User
We require a dedicated Windows Logon user for SmartSync. Specifically, this ensures that the SmartSync apps and services are run by a user with full access to all relevant areas of the server. This user must be able to lock their session as opposed to logging in and out.
- has Full Control on C:\ProgramData\BeanworksSyncTool
- has Full Control on the path(s) to your Company File(s)
For ease of use, we recommend including keywords like ‘SmartSync’ or ‘Beanworks’ in the username so it can be easily located & verified. You can refer to this article in our Help Centre to add a local user to your system.
Firewall Setup
SmartSync is both an SFTP client (data transfer) and an HTTPS client (authentication). Connections are initiated by the client, reaching out from your server to our infrastructure. Please ensure that the following traffic is allowed through your firewall, so SmartSync can send & receive data to our cloud infrastructure.
If your firewall is local to the installation machine, you may be able to whitelist using the combination of application name and port, or domain and port. If your firewall is at the perimeter, you may need to use the combination of machine name and port.
Domain or Service name | Port or Traffic type | Notes |
22000 (SFTP) | Port 22000 is specific to Quadient AP | |
443 (HTTPS Traffic) Outbound |
These authorizations are needed to allow SmartSync to do the following:
| |
Windows Executables: · SmartSync Manager · SmartSync Connector | ||
Windows Services: · SmartSync Connector Service · SmartSync Polling Service |
GP Synchronization User
SmartSync requires Microsoft Dynamics GP user credentials to communicate and sync data. Please create this user directly in the SQL server with DYNGRP roles in company and system databases. Do not create the user through Microsoft Dynamics GP ERP, as the ERP encrypts the credentials so that any non-System Admin user cannot log in to SQL server and access tables.
To create the DYNGRP User:
- Login to the SQL server using System Admin (sa) credentials
- Expand Security, right-click on Logins and choose New Login
- In the General Tab Choose SQL Server Authentication. Enter username and password
- Uncheck the 'user must change the password on next login' and 'enforce password expiration 'requirements
- In User Mapping mark the checkboxes for access to the following in the top table:
- corresponding Company Database (example BWGP1)
- GP System Database (usually called DYNAMICS)
- In the bottom table, assign the DYNGRP role to this user for the following:
- Company databases
- GP System Database
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article