Introduction:
This document will go through the functionality found within JetTrac QuickBooksConnect. This module can be used to dynamically creates folders from XML data.
Technical Support:
If you need assistance in installing and configuring JetTrac QuickBooksConnect™, call Pro Technology Automation, Inc. at 805-527-1248 or email us at support@protechinc.com. Please note that the JetTrac QuickBooksConnect™ license fee does not cover configuration services and technical support so there may be an additional charge. Please ensure you read these instructions carefully before calling for technical support.
How to run JetTracQuickBooksConnect:
After the JRE is installed, you can setup the JetTrac QuickBooksConnect files themselves. The files you need are:
- JTQuickBooksConnect.exe JetTrac QuickBooksConnect java executable program file
- ExitHandler.dll Required DLL
- HarborSIQB.dll Required DLL
- JTQuickBooksConnect.ini JetTrac QuickBooksConnect configuration INI file
Default Functionality:
Optional module to take data from any PDF form, e.g. a Work Order and automatically create invoices in QuickBooks for both header data and line item detail data. Can save a huge amount of time by automating the creation of QuickBooks invoices rather than manually creating invoices.
Job Step Configuration Window in JobConfig for JetTrac QuickBooksConnect:
When setting up a job step using JTQuickBooksConnect in JobConfig the only lines of the config you need to worry about are the first and the second to last, the Config file and the Input XML. If left as an asterisk * the input will be whatever file is in the data folder that triggered the job running. This works well if it’s the first step but if the input is also the output of a previous job step you would need to specify the fully qualified path of the input xml. All other fields should be filled with the fully qualified path to the intended file. Eg: C:\JetTrac\…\input.xml
In JobConfig, file paths entered should not be in quotes.
As with all modules, there is a dropdown to select whether or not the job should stop completely if this step fails. If you select Yes, any error will terminate the job process and write to the log file what happened, if no, then the job will try to continue anyways. However if any steps further down the line rely on the output of a job set to not stop on error, they may not work properly.
For more specifics go to the JetTrac Field ServiceJobConfig page.
JetTrac QuickBooksConnect Command Line:
QuickBooksConnect.exe Input.xml Configuration.ini JTQuickBooksConnect.log
“C:\JTQuickBooksConnect.exe” “””@InFile.”” “”@MDFName.”” “”@LogFile.””” “Creates new invoices in QuickBooks based on data in an XML file”
The command line begins with the file path to the module’s executable file, the path to the input XML, the path to the config file and the log file, then ends with a short description of what the module does.
JetTrac QuickBooksConnect Config.ini:
QuickBooksFile=C:\Users\Public\Documents\Intuit\QuickBooks\Sample Company Files\QuickBooks 2013\sample_service-based business.qbw
QuickBooksUser=@Admin
QuickBooksPassword=@
#QuickBooksInit=true
Customer=FacilityName
Job=”UST”
InvoiceDate=SignatureDate
PO=”1234″
Terms=”Net 30″
Rep=Rep
ShipDate=ShipDate
Via=Via
FOB=FOB
#Quantity=Quantity
#ItemCode=ItemCode
#Description=Description
#PriceEach=PriceEach
Class=Class
Amount=Amount
Tax=Tax
Memo=Memo
#
IgnoreIfBlank=Description
Additional Notes:
The first time you run the bat file to run the JetTrac QuickBooksConnect exe you will be prompted with a certification verification message. From the radio buttons you have to choose from select Yes, always; allow access even if QuickBooks is not running.
It is absolutely critical that the Customer field in the input XML matches EXACTLY to an existing Customer in QuickBooks. This is how JetTrac QuickBooksConnect knows.
ProTechnology can map data to standard QuickBooks fields but NOT custom fields.