Skip to content
English
  • There are no suggestions because the search field is empty.

Installing Fidesic Vendor Sync

Set up Fidesic Vendor Sync for Dynamics GP, or add another GP company to an existing setup

Overview

If this is your first time installing Vendor Sync, start at the beginning of this guide.

If you are adding an additional company to an existing setup, run the SQL script in that company's database first (see Create a SQL login for Vendor Sync), then skip to the Configuration section.

Preparation

  1. Users don't need to log out, and GP doesn't need to be shut down, to install Vendor Sync.
  2. The Fidesic Account Owner is needed to view the API keys that connect Vendor Sync to Fidesic.
  3. Vendor Sync can be installed on any machine that can reach your GP SQL Server. It runs as a Windows service on that machine and keeps Fidesic up to date with your GP vendors and chart of accounts, and with purchase orders and the other data you choose to sync.
  4. Do every step as a Windows administrator. Whenever you can "Run as administrator", do so.
  5. These instructions assume Vendor Sync is installed on the SQL Server machine. It can be installed on another machine on the network: just use the name or IP address of the SQL Server machine where this guide says "localhost".
  6. Have a SQL login ready for Vendor Sync. We recommend a dedicated login with only the permissions Vendor Sync needs, rather than sa. Create a SQL login for Vendor Sync shows how. Do it before the GP Database Integration step.
  7. Download the installer from the Fidesic downloads page: Fidesic Vendor Sync Service Installer.exe. Download it from that page each time rather than from a saved link, so you always get the latest version. api.fidesic.com/downloads/

Installation

  1. Right-click Fidesic Vendor Sync Service Installer.exe and choose Run as administrator. If an earlier version of Vendor Sync is installed, the installer upgrades it in place, so there's no need to uninstall it first. Your saved connections are kept.
  2. Follow the prompts for a standard installation.
  3. The Vendor Sync monitor opens when the installation finishes.
  4. To open it yourself later: C:\Program Files\Fidesic\Service Monitor\SyncMonitor.exe

Create a SQL login for Vendor Sync

Vendor Sync reads your GP data and writes only to its own tracking table, FIDESYNC. It never changes a GP table. A dedicated SQL login with the role the script below creates gives it exactly that access. The sa login also works, but we recommend a dedicated login.

  1. In SQL Server Management Studio, go to Security → Logins → New Login.
    New Login in SQL Server Management Studio
  2. Choose SQL Server authentication, enter a login name (for example fidesic_sync) and a password, and leave the Default database as master.
    Login name, password and default database
    Create the login in SQL Server, not in GP's User Setup: GP encrypts the passwords of logins it creates, so they don't work outside GP. Don't add the login to the DYNGRP role.
  3. Open the FIDESYNC_TABLE_AND_ROLE.sql script in a new query window and set @LoginName at the top to the login you created. Run it against your DYNAMICS database, then against every company database Vendor Sync will connect to. The script creates the FIDESYNC table and the FIDESYNC_ROLE role, adds the login to each database, and assigns it the role.
    Run it in a company database before you add that company in Vendor Sync. Vendor Sync can't sync a company whose FIDESYNC table is missing when it connects with a dedicated login.
  4. If you'd rather leave @LoginName blank, map the login yourself. In the login's User Mapping page, tick DYNAMICS and each company database Vendor Sync connects to, and select FIDESYNC_ROLE as the database role membership for each one.
    User Mapping with FIDESYNC_ROLE selected

The script is safe to run more than once. Run it again whenever you:

  • install or update Fidesic Vendor Sync
  • upgrade Dynamics GP
  • add a new company to sync

What the script grants

  • Each company database: read (SELECT) access to the GP tables and views in the dbo schema. The grant covers the whole schema, not a list of tables, so it keeps working after a GP upgrade rebuilds tables, and new Vendor Sync features work without another grant.
  • Each company database: SELECT, INSERT, UPDATE, DELETE and ALTER on the FIDESYNC table only. ALTER lets a newer Vendor Sync add a tracking column to that one table.
  • Each company database, if the Fidesic GP add-in's Multi-Entity Management procedure (zDP_FIDMEM) is installed: permission to see that it exists, so Vendor Sync can report it. Vendor Sync never runs it.
  • DYNAMICS: SELECT on DB_Upgrade and SY01500, which Vendor Sync uses to report your GP version and company name to Fidesic.
  • Server: nothing.

Configuration

  • Vendor Sync runs in the taskbar as a green dot. Double-click it to open the configuration window.
  • Select Setup: Configure.

mceclip4.png

GP Database Integration

  1. Connection: Add New.... This is also how you add a connection to an existing setup.
  2. Server: "localhost" if Vendor Sync is installed on the SQL Server machine. If not, the name or IP address of the SQL Server machine.
  3. Username: the SQL login you created for Vendor Sync (or sa).
  4. Password: that login's password.
  5. Catalog: select your GP company database. The list shows every database on the server, so pick one you ran the script against.mceclip0.png

Fidesic Authentication

In this window, the "Username" is the API key, and the "Password" is the API password. Click here to learn how to get this information from Fidesic. The Account Owner is the only user with access to these keys within Fidesic. The account owner is tagged as such in the users list in Fidesic.

mceclip2.png

If you enter the right keys and get a "cannot authenticate" message, check that this machine can reach api.fidesic.com.

Advanced Settings

  • First Sync: Selected automatically after install, and cleared automatically after the first sync. While it's selected, Vendor Sync checks every vendor record instead of only new and changed ones.
  • Sync Chart of Accounts: Also sends your GL accounts and each vendor's default GL accounts.
  • Sync Purchase Orders: Also sends your open purchase orders from GP.
  • Sync Temporary Vendors: Also sends temporary vendors. Off by default.
  • Vendor Classes To Exclude: Vendor classes to leave out of the sync, separated by commas.
  • Log errors to file: Writes a log file to the C:\Program Files\Fidesic\Sync Service\Logs folder on this machine, with every connection attempt and any errors. Don't leave it on permanently: it's meant for troubleshooting. It creates one file per day, which gradually takes up disk space.

mceclip3.png

Sync Chart of Accounts and Sync Purchase Orders can also be changed in Fidesic, at Settings → Company → Preferences, in the GP Vendor Sync panel. A change made on either side reaches the other. That panel also has settings that are only in Fidesic, such as how often Vendor Sync runs and tax details. Sync Temporary Vendors, Vendor Classes To Exclude and Log errors to file show in that panel only for Fidesic support, so change them here in the Vendor Sync monitor, or ask Fidesic support. To sync offline payments or historical invoices from GP, or to reset the sync, ask Fidesic support.

Troubleshooting a dedicated SQL login

  • The Catalog list is empty, or shows only master and tempdb. Your SQL Server has been set up so that logins can't see other databases' names. Run GRANT VIEW ANY DATABASE TO [fidesic_sync]; in the master database, using your login's name. It lets the login see database names only, not their data.
  • The log shows "CREATE TABLE permission denied". The script hasn't been run in that company database. Run it there; the company syncs on the next cycle.
  • Fidesic doesn't show your GP version or company name. The script hasn't been run against DYNAMICS, or the login isn't mapped to it. Syncing still works without it. Vendor Sync reads these from a system database named DYNAMICS.

FIDESYNC_TABLE_AND_ROLE.sql

Copy the whole script into a new query window in SQL Server Management Studio.

/*
*    FIDESYNC Installation / Update script  (Fidesic Vendor Sync for GP)
*    Script version 2026-11-16. Works with every Vendor Sync version; checked against 2.11.1.
*
*    Changed from the previous version (headed "Vendor Sync for GP 2.2+"):
*      - Creates the FIDESYNC.ROW_HASH column that Vendor Sync 2.6.0 and later use. Before,
*        the service added it on its first run, through the ALTER permission below.
*      - Creates the service's database user with dbo as its default schema.
*      - Says so and skips the role step when the login owns the database, instead of failing.
*      - Lets the service see the GP add-in's MEM procedure (zDP_FIDMEM), whether it is
*        installed being part of the status Vendor Sync reports to Fidesic.
*      Nothing granted by an earlier version is taken away, so it is safe to run over one.
*
*    Safe to run more than once. Use it for a new install, after updating Vendor Sync,
*    after a Dynamics GP upgrade, and whenever you add a company to sync.
*
*    What it does:
*      System database (DYNAMICS):  creates FIDESYNC_ROLE and grants SELECT on the
*                                  GP version (DB_Upgrade) and company list (SY01500) tables.
*      Each company database:      creates or updates the FIDESYNC tracking table,
*                                  creates FIDESYNC_ROLE, grants SELECT on the dbo schema
*                                  (every GP table and view, including ones added later),
*                                  and grants read/write on FIDESYNC.
*
*    Instructions:
*      1. Create a SQL Server login for the service (Security > Logins), if you have not already.
*        Use SQL Server authentication and leave its default database as master.
*        Do not create it as a GP user, and do not add it to DYNGRP.
*      2. Optional: set @LoginName below to that login. The script then adds the login as a user
*        in this database and assigns it to FIDESYNC_ROLE. Leave it blank to do that by hand.
*      3. Run this script against the DYNAMICS database and against EVERY company database
*        that Vendor Sync connects to, before you add that company in Vendor Sync.
*/

DECLARE @LoginName sysname = N'';  -- e.g. N'fidesic_sync'

SET NOCOUNT ON;

/****** CREATE FIDESYNC ROLE ******/
IF DATABASE_PRINCIPAL_ID('FIDESYNC_ROLE') IS NULL
BEGIN
    CREATE ROLE [FIDESYNC_ROLE];
    PRINT 'Created FIDESYNC_ROLE role';
END

/****** OPTIONAL: ADD THE SERVICE LOGIN TO THIS DATABASE AND THE ROLE ******/
IF LEN(@LoginName) > 0
BEGIN
    IF SUSER_ID(@LoginName) IS NULL
    BEGIN
        RAISERROR('Login %s does not exist on this server. Create it first, then rerun.', 16, 1, @LoginName);
        RETURN;
    END

    DECLARE @sql nvarchar(max);
    -- The login may already be mapped to this database under a different user name.
    DECLARE @UserName sysname = (SELECT name FROM sys.database_principals WHERE sid = SUSER_SID(@LoginName));

    IF @UserName IS NULL
    BEGIN
        SET @UserName = @LoginName;
        SET @sql = N'CREATE USER ' + QUOTENAME(@UserName) + N' FOR LOGIN ' + QUOTENAME(@LoginName) + N' WITH DEFAULT_SCHEMA = [dbo]';
        EXEC sp_executesql @sql;
        PRINT 'Added user ' + @UserName + ' to ' + DB_NAME();
    END

    IF @UserName = N'dbo'
        PRINT 'Login ' + @LoginName + ' owns ' + DB_NAME() + ', so it is not added to FIDESYNC_ROLE. Use a login that does not own the database.';
    ELSE IF IS_ROLEMEMBER('FIDESYNC_ROLE', @UserName) = 0
    BEGIN
        SET @sql = N'ALTER ROLE [FIDESYNC_ROLE] ADD MEMBER ' + QUOTENAME(@UserName);
        EXEC sp_executesql @sql;
        PRINT 'Added ' + @UserName + ' to FIDESYNC_ROLE';
    END
END

/****** SYSTEM DATABASE: GP version and company name lookups ******/
-- SY01500 (company master) exists only in the GP system database.
IF OBJECT_ID(N'dbo.SY01500', N'U') IS NOT NULL
BEGIN
    GRANT SELECT ON dbo.SY01500 TO [FIDESYNC_ROLE];
    IF OBJECT_ID(N'dbo.DB_Upgrade', N'U') IS NOT NULL
        GRANT SELECT ON dbo.DB_Upgrade TO [FIDESYNC_ROLE];
    PRINT 'Granted SELECT on DB_Upgrade and SY01500 to FIDESYNC_ROLE';
    PRINT 'Finished system database ' + DB_NAME() + '. Now run this script against each company database.';
    RETURN;
END

/****** COMPANY DATABASE: FIDESYNC TRACKING TABLE ******/
IF OBJECT_ID(N'dbo.FIDESYNC', N'U') IS NULL
BEGIN
    CREATE TABLE dbo.FIDESYNC(
        ID INT IDENTITY PRIMARY KEY,
        TableName NVARCHAR(50) NOT NULL,
        TableKey NVARCHAR(50) NOT NULL,
        LAST_SYNC DATETIME NOT NULL,
        FAILED_ATTEMPT DATETIME,
        FAILED_COUNT INT NOT NULL DEFAULT 0,
        ROW_HASH VARBINARY(32) NULL);
    PRINT 'Created FIDESYNC table';
END
ELSE
    PRINT 'FIDESYNC table already exists';

IF COL_LENGTH(N'dbo.FIDESYNC', N'FAILED_ATTEMPT') IS NULL
    ALTER TABLE dbo.FIDESYNC ADD FAILED_ATTEMPT DATETIME;
IF COL_LENGTH(N'dbo.FIDESYNC', N'FAILED_COUNT') IS NULL
    ALTER TABLE dbo.FIDESYNC ADD FAILED_COUNT INT NOT NULL DEFAULT 0;
-- Change tracking for GP tables that have no timestamp (tax details and schedules), Vendor Sync 2.6.0+
IF COL_LENGTH(N'dbo.FIDESYNC', N'ROW_HASH') IS NULL
BEGIN
    ALTER TABLE dbo.FIDESYNC ADD ROW_HASH VARBINARY(32) NULL;
    PRINT 'Added ROW_HASH to FIDESYNC';
END

/****** COMPANY DATABASE: PERMISSIONS ******/
-- A schema-level grant covers every current GP table and view, and also tables created later
-- (a GP upgrade rebuilds tables, and Analytical Accounting can be installed later). Grants on
-- individual tables are lost when a table is rebuilt.
GRANT SELECT ON SCHEMA::dbo TO [FIDESYNC_ROLE];
PRINT 'Granted SELECT on all GP tables and views (dbo schema) to FIDESYNC_ROLE';

-- ALTER lets a later Vendor Sync add a tracking column to this one table without rerunning the script.
GRANT SELECT, INSERT, UPDATE, DELETE, ALTER ON dbo.FIDESYNC TO [FIDESYNC_ROLE];
PRINT 'Granted SELECT, INSERT, UPDATE, DELETE, ALTER on FIDESYNC to FIDESYNC_ROLE';

-- Vendor Sync reports whether the GP add-in's MEM procedure is installed. It only checks that the
-- procedure exists and never runs it, but without a permission on it the login cannot see it.
IF OBJECT_ID(N'dbo.zDP_FIDMEM', N'P') IS NOT NULL
BEGIN
    GRANT VIEW DEFINITION ON dbo.zDP_FIDMEM TO [FIDESYNC_ROLE];
    PRINT 'Granted VIEW DEFINITION on zDP_FIDMEM to FIDESYNC_ROLE';
END

PRINT '';
PRINT 'Finished company database ' + DB_NAME() + '.';
IF LEN(@LoginName) = 0
    PRINT 'Next: add the service login as a user in this database and assign it to FIDESYNC_ROLE.';