WM-Synergy - Avalara Tax - Migration

WM-Synergy - Avalara Tax - Migration


Install Schema

Run the ScriptInstall.exe executable to get the database tables, triggers, and functions put in place. 
This is found where the Tax Connector is installed.. IE: D:\Visual\localapps\webservices\SynergyTax\SynergyTax\ScriptInstall\




Import Macro's




The XML is usually found in D:\Visual\localapps\webservices\SynergyTax\TaxMacros (you'll want TaxSQLServer.xml to import)





After steps 1 and 2 are complete, take the attached .sql file and open it in SQL Server management studio.  This will move the data from 1 database to another but some mods will have to be done.

Example
To migrate from a database called Pilot1 to Pilot2, do a search and replace for LIVEDB and change it to PILOT2.  Do a search and replace for TESTDB and change to PILOT1.  

You will then need to configure JobQ service for the production DB


    • Related Articles

    • WM-Synergy - Avalara Tax - Release Notes

      v1100.1003 2025.05.11 Add more diagnostic to validate the shipping address sent mod to SRI Macros SRITAX/SRITAXC to better handle an empty Avalara return data packet Add <line1><line2><line3> to the request packet information for traceability in ...

    • WM-Synergy - Avalara Tax Connector - Version Info

      To Find the version of Synergy Tax. Launch Visual Manufacturing Navigate to Sales > Customer Maintenance > Macros Menu >Tax Configuration The bottom of the Tax Configuration Screen will have the version number.

    • WM-Synergy - Avalara Tax - Visual to Avalara Mapping

    • WM-Synergy - Avalara Tax - Version Number

      To get the version number of Tax that the customer is using, go into the Visual directory of the server that tax is running on (e.g. "E:\Visual"). From there, go into \Localapps\Webservices\SynergyTax and run WebAppUpdateUtility.exe. A window will ...

    • WM-Synergy - Avalara Tax - Process Flow

      Order Entry Shipping Invoice Generation Technical Notes: During the install, a Windows Service (Synergy Job Queue) and database tables & triggers are created. These triggers interact with the Windows service to run the tasks without the need for a ...