Production process to pull data from Google Sheets and update other systems.
If you need assistance in installing and configuring JetTrac PullFromGoogleSheets™, call Pro Technology Automation, Inc. at 805-527-1248 or email us at email@example.com. Please note that the JetTrac PullFromGoogleSheets™ 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.
From a job step in JetTrac JobController.
To run JTPullFromGoogleSheets, you need 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 pull of data from Google Sheets to a CSV file or XML
When setting up a job step using JTPullFromGoogleSheets in JobConfig the only line of the config you need to worry about is the first, the Config file. This should be filled with the fully qualified path to the Config file for JTPullFromGoogleSheets. Eg: C:\JetTrac\…\config.ini
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.
“C:\JetTrac\Programs\JTPullFromGoogleSheets\JTPullFromGoogleSheets.exe” “Google Sheet ID” “C:\Output.csv” “”C:\JTPullFromGoogleSheets.log“
The command line begins with the file path to the module’s executable file followed by the ID of the Google sheet being accessed, the desired path and name of the output CSV file, and the path to the log file. The line ends with a short description of what the module does.
The test.csv will be created from the header and data information in the google sheet.