Easily captures data submitted from PDF forms to Google Sheets that can be reviewed and approved before data is submitted to other systems
If you need assistance in installing and configuring JetTrac PushToGoogleSheets™, call Pro Technology Automation, Inc. at 805-527-1248 or email us at email@example.com. Please note that the JetTrac PushToGoogleSheets™ 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.
A bat file or job step in Job Controller can execute this module.
To run JTPushToGoogleSheets, you will need to have these files in the same folder:
Executable files should not be edited for any reason.
All google modules need to be authorized to be allowed to run. To do this, make sure you are logged into the proper google account you want JetTrac to access, then run the Google Modules Authorization .bat file. It will ask you to log in and allow access to JetTrac to use the account. This only needs to be done once as the file will authorize all google modules.
Server-side updating of Google Sheets from data in an XML file that is collected from PDF forms
When setting up a job step using JTPushToGoogleSheets 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 to be written to a spreadsheet in Google Sheets. 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 BYODJobConfig page.
“C:\JTPushToGoogleSheets.exe” “C:\JTPushToGoogleSheets_Input.xml” “C:\JTPushToGoogleSheets.ini” “C:\JTPushToGoogleSheets.log”
The command line begins with the file path to the module’s executable file followed by the path to the input XML file, the path to the config file, and the log file. Each part is the fully qualified path to the file, in quotes, and separated by a space.
spreadsheetKey= “Static Key from GoogleSheet URL” or XMLTag Name ( without the < > Symbols )
worksheetName=”Static Text” or XMLTag Name ( without the < > Symbols )
columnHeaders=”Static Text”|”Static Text” (Must match Google Sheet Headers)
values=”Static Text”|XMLTagName (Must match XML Tags)
as an example:
spreadsheetKey= “1TmxybIJ_f9_kAKiWXAIa0dxX7Z_EuM7FnuiwTlmLJ90” or GoogleSheetKey
worksheetName=”Adobe Systems Inc.” or Accounts
values=”PTA Invoice 8168 Adobe Training “|Training
IMPORTANT: JTGooglePushToGoogleSheets will fail if there are any modifications one of the corresponding/matching field references. This includes being case sensitive.
eg. Change the Header name in the Google Sheet on its own will fail. You can remedy this by matching the names either way.