TachoSync Integrations - Revision history

Donatas.Mazonas at 10:25, 9 February 2026

2026-02-09T10:25:44Z

← Older revision		Revision as of 13:25, 9 February 2026
Line 172:		Line 172:
	* The [[TachoSync Integrations#Prerequisites\|prerequisites]] are met.		* The [[TachoSync Integrations#Prerequisites\|prerequisites]] are met.
	* SFTP server internet connection is stable (there are no repeating time-outs or interruptions).		* SFTP server internet connection is stable (there are no repeating time-outs or interruptions).
	* TachoSync has the neccessary permissions to create folders and upload files.		* TachoSync has the neccessary permissions to create folders and upload files in your SFTP server.
	* The provided path exists on the server.		* The provided path exists on the server.
	If issues persist, collect the “Last event” details from the Integrations page and contact Support.		If issues persist, collect the “Last event” details from the Integrations page and contact Support.

	[[Category:TachoSync]]		[[Category:TachoSync]]

Evaldas.M at 12:59, 6 February 2026

2026-02-06T12:59:48Z

← Older revision		Revision as of 15:59, 6 February 2026
Line 171:		Line 171:
	If the SFTP integration does not work as expected, verify the following:		If the SFTP integration does not work as expected, verify the following:
	* The [[TachoSync Integrations#Prerequisites\|prerequisites]] are met.		* The [[TachoSync Integrations#Prerequisites\|prerequisites]] are met.
	* ~~Your~~ internet connection is stable (there are no repeating time-outs or interruptions).		* SFTP server internet connection is stable (there are no repeating time-outs or interruptions).
	* ~~The user~~ has ~~write~~ permissions ~~for the configured directory~~.		* TachoSync has the neccessary permissions to create folders and upload files.
	* The provided path exists on the server.		* The provided path exists on the server.
	If issues persist, collect the “Last event” details from the Integrations page and contact Support.		If issues persist, collect the “Last event” details from the Integrations page and contact Support.

	[[Category:TachoSync]]		[[Category:TachoSync]]

Donatas.Mazonas: /* Folder Structure Examples */

2026-02-06T11:51:25Z

Folder Structure Examples

← Older revision		Revision as of 14:51, 6 February 2026
Line 141:		Line 141:
	* /base_folder/MainCompany/SubCompany/Department		* /base_folder/MainCompany/SubCompany/Department
	** /Vehicles		** /Vehicles
	*** /ABC123 ''← vehicle folder		*** /ABC123 ''← vehicle folder''
	**** M_YYYYMMDD_HHmm_ABC123_VIN.DDD ← vehicle file		**** M_YYYYMMDD_HHmm_ABC123_VIN.DDD ← vehicle file
	**** …		**** …
	** /Drivers		** /Drivers
	*** /1234567890/ ''← driver folder		*** /1234567890''← driver folder''
	**** C_YYYYMMDD_HHmm_N_SURNAME_1234567890.DDD← driver file		**** C_YYYYMMDD_HHmm_N_SURNAME_1234567890.DDD← driver file
	**** …		**** …

Donatas.Mazonas: /* Folder Structure Examples */

2026-02-06T11:44:08Z

Folder Structure Examples

← Older revision		Revision as of 14:44, 6 February 2026
Line 139:		Line 139:
	<tr>		<tr>
	<td style="vertical-align: top; text-align: left;">		<td style="vertical-align: top; text-align: left;">
	* /base_folder		* /base_folder/MainCompany/SubCompany/Department
	** /MainCompany		** /Vehicles
	~~***~~ /SubCompany		*** /ABC123 ''← vehicle folder
	~~****~~ /Department		**** M_YYYYMMDD_HHmm_ABC123_VIN.DDD ← vehicle file
	~~*~~ /Vehicles		**** …
	~~*~~* /ABC123 ''← vehicle folder		** /Drivers
	~~*~~** M_YYYYMMDD_HHmm_ABC123_VIN.DDD ← vehicle file		*** /1234567890/ ''← driver folder
	~~*~~** …		**** C_YYYYMMDD_HHmm_N_SURNAME_1234567890.DDD← driver file
	~~*~~ /Drivers		**** …
	~~*~~* /1234567890/ ''← driver folder
	~~*~~** C_YYYYMMDD_HHmm_N_SURNAME_1234567890.DDD← driver file
	~~*~~** …
	</td>		</td>
	<td style="vertical-align: top; text-align: left;">		<td style="vertical-align: top; text-align: left;">
	* /base_folder		* /base_folder/MainCompany/SubCompany/Department
	** /MainCompany		** /Vehicles
	~~***~~ /SubCompany		*** /ABC123 ''← vehicle folder
	~~****~~ /Department		**** M_YYYYMMDD_HHmm_ABC123_VIN.DDD ← vehicle file
	~~*~~ /Vehicles		**** C_YYYYMMDD_HHmm_N_SURNAME_1234567890.DDD← driver file
	~~*~~* /ABC123 ''← vehicle folder		**** …
	~~*~~** M_YYYYMMDD_HHmm_ABC123_VIN.DDD ← vehicle file
	~~*~~** C_YYYYMMDD_HHmm_N_SURNAME_1234567890.DDD← driver file
	~~*~~** …
	</td>		</td>
	</tr>		</tr>
	</table>		</table>

	===File Upload Behavior===		===File Upload Behavior===
	TachoSync uploads files to your SFTP server as soon as they become available in TachoSync (after being downloaded from device):		TachoSync uploads files to your SFTP server as soon as they become available in TachoSync (after being downloaded from device):

Donatas.Mazonas at 11:41, 6 February 2026

2026-02-06T11:41:03Z

← Older revision		Revision as of 14:41, 6 February 2026
Line 55:		Line 55:
	** New files are processed.		** New files are processed.
	** Failed files remain as "Failed" until a successful retry.		** Failed files remain as "Failed" until a successful retry.
	** '''The user can try to [[#SFTP Integration Troubleshooting\|fix the connection]] and manually retry the connection''.		** ''The user can try to [[#SFTP Integration Troubleshooting\|fix the connection]] and manually retry the connection''.
	* '''Failed''' – integration has failed:		* '''Failed''' – integration has failed:
	** One or more file transfers have failed AND no file transfer has been successful:		** One or more file transfers have failed AND no file transfer has been successful:
Line 101:		Line 101:
	<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">		<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
	<tr>		<tr>
	<th style="width:50%; vertical-align: middle; text-align: left;">VEHICLE FILES</th>		<th style="width:40%; vertical-align: middle; text-align: left;">VEHICLE FILES</th>
	<th style="width:50%; vertical-align: middle; text-align: left;">DRIVER FILES</th>		<th style="width:40%; vertical-align: middle; text-align: left;">DRIVER FILES</th>
	</tr>		</tr>
	<tr>		<tr>
Line 109:		Line 109:
	</tr>		</tr>
	<tr>		<tr>
	<td style="vertical-align: ~~middle~~; text-align: left;">		<td style="vertical-align: top; text-align: left;">
	M – vehicle (mass memory) data<br>YYYYMMDD – download date (UTC)<br>HHmm – download time (UTC)<br>VEHICLEREGNUMBER – vehicle registration number<br>VIN – vehicle identification number		M – vehicle (mass memory) data<br>YYYYMMDD – download date (UTC)<br>HHmm – download time (UTC)<br>VEHICLEREGNUMBER – vehicle registration number<br>VIN – vehicle identification number
	</td>		</td>
	<td style="vertical-align: ~~middle~~; text-align: left;">		<td style="vertical-align: top; text-align: left;">
	C – driver card data<br>YYYYMMDD – download date (UTC)<br> HHmm – download time (UTC)<br>N – first letter of driver’s first name<br>SURNAME – driver’s surname<br>CARDNUMBER – driver card number		C – driver card data<br>YYYYMMDD – download date (UTC)<br> HHmm – download time (UTC)<br>N – first letter of driver’s first name<br>SURNAME – driver’s surname<br>CARDNUMBER – driver card number
	</td>		</td>
Line 118:		Line 118:
	</table>		</table>
	====Folder Logic====		====Folder Logic====
	''Each SFTP integration has a base folder'', configured in the field "Remote directory path". Inside this base folder, the system always creates folders that reflect your company hierarchy, e.g. <code>base_folder/MainCompany/SubCompany/Department/…</code>.		''Each SFTP integration has a base folder'', configured in the field "Remote directory path".

			Inside this base folder, the system always creates folders that reflect your company hierarchy, e.g. <code>base_folder/MainCompany/SubCompany/Department/…</code>.

	Beyond company structure, '''the “Driver file destination“ setting determines how folders are structured:'''		Beyond company structure, '''the “Driver file destination“ setting determines how folders are structured:'''
Line 126:		Line 128:
	* If you choose to store driver files in the vehicle folder '''(option “Vehicle folder”) - separate folders are NOT created. Under the company hierarchy, only specific vehicle folders are created''' (named according to vehicle IMEI/number).		* If you choose to store driver files in the vehicle folder '''(option “Vehicle folder”) - separate folders are NOT created. Under the company hierarchy, only specific vehicle folders are created''' (named according to vehicle IMEI/number).
	** Both driver and vehicle files are placed under these specific vehicle folders.		** Both driver and vehicle files are placed under these specific vehicle folders.
	*** To correctly place driver files under a vehicle folder, the system determines which vehicle the driver is operating.		** To correctly place driver files under a vehicle folder, the system determines which vehicle the driver is operating.

	====Folder Structure Examples====		====Folder Structure Examples====
Line 136:		Line 138:
	</tr>		</tr>
	<tr>		<tr>
	<td style="vertical-align: ~~middle~~; text-align: left;">		<td style="vertical-align: top; text-align: left;">
	* /base_folder		* /base_folder
	** /MainCompany		** /MainCompany
Line 150:		Line 152:
	******* …		******* …
	</td>		</td>
	<td style="vertical-align: ~~middle~~; text-align: left;">		<td style="vertical-align: top; text-align: left;">
	* /base_folder		* /base_folder
	** /MainCompany		** /MainCompany
Line 171:		Line 173:

	To troubleshoot, see [[TachoSync Integrations#SFTP Integration Troubleshooting\|SFTP Integration Troubleshooting]].		To troubleshoot, see [[TachoSync Integrations#SFTP Integration Troubleshooting\|SFTP Integration Troubleshooting]].

	===SFTP Integration Troubleshooting===		===SFTP Integration Troubleshooting===
	If the SFTP integration does not work as expected, verify the following:		If the SFTP integration does not work as expected, verify the following:

Donatas.Mazonas: Formatting edits after major SFTP update.

2026-02-06T11:36:34Z

Formatting edits after major SFTP update.

← Older revision		Revision as of 14:36, 6 February 2026
Line 55:		Line 55:
	** New files are processed.		** New files are processed.
	** Failed files remain as "Failed" until a successful retry.		** Failed files remain as "Failed" until a successful retry.
	** '''The user can try to [[#SFTP Integration Troubleshooting\|fix the connection]] and manually retry the connection'''.		** '''The user can try to [[#SFTP Integration Troubleshooting\|fix the connection]] and manually retry the connection''.
	* '''Failed''' – integration has failed:		* '''Failed''' – integration has failed:
	** One or more file transfers have failed AND no file transfer has been successful:		** One or more file transfers have failed AND no file transfer has been successful:
	*** New files are processed.		*** New files are processed nevertheless.
	** Alternatively, the integration has failed the connection test.		** Alternatively, the integration has failed the connection test.
	*** Integration is skipped when files are queued, no uploads are attempted.		*** Integration is skipped when files are queued, no uploads are attempted.
	** '''The user can try to [[#SFTP Integration Troubleshooting\|fix the connection]] and manually retry the connection'''.		** ''The user can try to [[#SFTP Integration Troubleshooting\|fix the connection]] and manually retry the connection.''

	===SFTP Server Settings===		===SFTP Server Settings===
	[[File:TachoSync Integrations settings.png\|thumb\|right\|alt=TachoSync Integrations settings\|TachoSync SFTP integration settings]]		[[File:TachoSync Integrations settings.png\|thumb\|right\|alt=TachoSync Integrations settings\|TachoSync SFTP integration settings]]
Line 100:		Line 99:

	====File Naming Schema====		====File Naming Schema====
	* Vehicle files <code>M_YYYYMMDD_HHmm_VEHICLEREGNUMBER_VIN.DDD</code>		<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
	** M – vehicle (mass memory) data		<tr>
	** YYYYMMDD – download date (UTC)		<th style="width:50%; vertical-align: middle; text-align: left;">VEHICLE FILES</th>
	** HHmm – download time (UTC)		<th style="width:50%; vertical-align: middle; text-align: left;">DRIVER FILES</th>
	** VEHICLEREGNUMBER – vehicle registration number		</tr>
	** VIN – vehicle identification number		<tr>
	* Driver files		<td style="vertical-align: middle; text-align: left;"><code>M_YYYYMMDD_HHmm_VEHICLEREGNUMBER_VIN.DDD</code></td>
	<~~code~~>~~C_YYYYMMDD_HHmm_N_SURNAME_CARDNUMBER.DDD~~<~~/code~~>		<td style="vertical-align: middle; text-align: left;"><code>C_YYYYMMDD_HHmm_N_SURNAME_CARDNUMBER.DDD</code></td>
	** C – driver card data		</tr>
	** YYYYMMDD – download date (UTC)		<tr>
	** HHmm – download time (UTC)		<td style="vertical-align: middle; text-align: left;">
	** N – first letter of driver’s first name		M – vehicle (mass memory) data<br>YYYYMMDD – download date (UTC)<br>HHmm – download time (UTC)<br>VEHICLEREGNUMBER – vehicle registration number<br>VIN – vehicle identification number
	** SURNAME – driver’s surname		</td>
	** CARDNUMBER – driver card number		<td style="vertical-align: middle; text-align: left;">
			C – driver card data<br>YYYYMMDD – download date (UTC)<br> HHmm – download time (UTC)<br>N – first letter of driver’s first name<br>SURNAME – driver’s surname<br>CARDNUMBER – driver card number
			</td>
			</tr>
			</table>
	====Folder Logic====		====Folder Logic====

	''Each SFTP integration has a base folder'', configured in the field "Remote directory path". Inside this base folder, the system always creates folders that reflect your company hierarchy, e.g. <code>base_folder/MainCompany/SubCompany/Department/…</code>.		''Each SFTP integration has a base folder'', configured in the field "Remote directory path". Inside this base folder, the system always creates folders that reflect your company hierarchy, e.g. <code>base_folder/MainCompany/SubCompany/Department/…</code>.

	Beyond company structure, '''the “Driver file destination“ setting determines how folders are structured'''~~''Italic text'':~~		Beyond company structure, '''the “Driver file destination“ setting determines how folders are structured:'''
	~~'''~~* If you choose to store driver files in a separate driver folder (option “Driver folder”)~~:'''~~		* If you choose to store driver files in a separate driver folder '''(option “Driver folder”) - two separate folders named “Drivers” and “Vehicles” are created.'''
	~~'''** Two~~ separate folders named “Drivers” and “Vehicles” are created.'''
	** In these folders, subfolders are created according to driver card and vehicle IMEI/number, respectively.		** In these folders, subfolders are created according to driver card and vehicle IMEI/number, respectively.
	** Files are placed accordingly.		** Files are placed accordingly.
	~~'''~~* If you choose to store driver files in the vehicle folder (option “Vehicle folder”)~~:'''~~		* If you choose to store driver files in the vehicle folder '''(option “Vehicle folder”) - separate folders are NOT created. Under the company hierarchy, only specific vehicle folders are created''' (named according to vehicle IMEI/number).
	~~'''** Separate “Drivers” and “Vehicles”~~ folders are NOT created.~~'''~~		** Both driver and vehicle files are placed under these specific vehicle folders.
	'''** Under the company hierarchy, only specific vehicle folders are created''' (named according to vehicle IMEI/number).		*** To correctly place driver files under a vehicle folder, the system determines which vehicle the driver is operating.
	** Both driver and vehicle files are placed under these specific vehicle folders. To correctly place driver files under a vehicle folder, the system determines which vehicle the driver is operating.

	====Folder Structure Examples====		====Folder Structure Examples====
	Assuming “Vehicles folder naming” = “Vehicle number” and .DDD file format.		Assuming “Vehicles folder naming” = “Vehicle number” and .DDD file format.
			<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
	# Driver file destination = Driver folder		<tr>
			<th style="width:50%; vertical-align: middle; text-align: left;">Driver file destination = Driver folder</th>
			<th style="width:50%; vertical-align: middle; text-align: left;">Driver file destination = Vehicle folder</th>
			</tr>
			<tr>
			<td style="vertical-align: middle; text-align: left;">
	* /base_folder		* /base_folder
	** /MainCompany		** /MainCompany
Line 145:		Line 149:
	******* C_YYYYMMDD_HHmm_N_SURNAME_1234567890.DDD← driver file		******* C_YYYYMMDD_HHmm_N_SURNAME_1234567890.DDD← driver file
	******* …		******* …
			</td>
	~~# Driver file destination~~ = ~~Vehicle folder~~		<td style="vertical-align: middle; text-align: left;">
	* /base_folder		* /base_folder
	** /MainCompany		** /MainCompany
Line 156:		Line 160:
	******* C_YYYYMMDD_HHmm_N_SURNAME_1234567890.DDD← driver file		******* C_YYYYMMDD_HHmm_N_SURNAME_1234567890.DDD← driver file
	******* …		******* …
			</td>
			</tr>
			</table>
	===File Upload Behavior===		===File Upload Behavior===
	TachoSync uploads files to your SFTP server as soon as they become available in TachoSync (after being downloaded from device):		TachoSync uploads files to your SFTP server as soon as they become available in TachoSync (after being downloaded from device):

Donatas.Mazonas: typos

2026-02-06T11:20:04Z

typos

← Older revision		Revision as of 14:20, 6 February 2026
Line 127:		Line 127:
	'''** Separate “Drivers” and “Vehicles” folders are NOT created.'''		'''** Separate “Drivers” and “Vehicles” folders are NOT created.'''
	'''** Under the company hierarchy, only specific vehicle folders are created''' (named according to vehicle IMEI/number).		'''** Under the company hierarchy, only specific vehicle folders are created''' (named according to vehicle IMEI/number).
	** Both driver and vehicle files are placed under these specific vehicle folders. To correctly place driver files under a vehicle folder, the system ~~must determine~~ which vehicle the driver is operating:		** Both driver and vehicle files are placed under these specific vehicle folders. To correctly place driver files under a vehicle folder, the system determines which vehicle the driver is operating.
	*** The system checks vehicle information included in the driver file.
	*** If vehicle information is not available in the driver file, the system places that driver file under the last known vehicle folder.
	*** If this last known vehicle cannot be determined, the file is not uploaded (upload status set to “Failed”).

	====Folder Structure Examples====		====Folder Structure Examples====
Line 146:		Line 143:
	***** /Drivers		***** /Drivers
	****** /1234567890/ ''← driver folder		****** /1234567890/ ''← driver folder
	******* C_YYYYMMDD_HHmm_N_SURNAME_1234567890.~~DD←~~ driver file		******* C_YYYYMMDD_HHmm_N_SURNAME_1234567890.DDD← driver file
	******* …		******* …

Line 157:		Line 154:
	****** /ABC123 ''← vehicle folder		****** /ABC123 ''← vehicle folder
	******* M_YYYYMMDD_HHmm_ABC123_VIN.DDD ← vehicle file		******* M_YYYYMMDD_HHmm_ABC123_VIN.DDD ← vehicle file
	******* C_YYYYMMDD_HHmm_N_SURNAME_1234567890.~~DD←~~ driver file		******* C_YYYYMMDD_HHmm_N_SURNAME_1234567890.DDD← driver file
	******* …		******* …

Donatas.Mazonas: whoops

2026-02-06T08:54:11Z

whoops

@@ Line 5: / Line 5: @@
 * [[TachoSync Integrations#SFTP|SFTP]]
 Additional integration methods are in development.
 ==Integrations Menu==

Donatas.Mazonas: Reworked some places, expanded on folder and file naming structure. [GTPGTM-10958]

2026-02-06T08:51:44Z

Reworked some places, expanded on folder and file naming structure. [GTPGTM-10958]

Show changes

Donatas.Mazonas: /* SFTP Integration Status Descriptions */

2026-02-04T14:03:21Z

SFTP Integration Status Descriptions

← Older revision		Revision as of 17:03, 4 February 2026
Line 47:		Line 47:
	** No failed file transfers.		** No failed file transfers.
	** New (and historical, if enabled) files are queued and uploaded.		** New (and historical, if enabled) files are queued and uploaded.
	• Disabled - integration is disabled by the user:		* '''Disabled''' - integration is disabled by the user:
	** No files are queued or uploaded.		** No files are queued or uploaded.
	** No retries can occur.		** No retries can occur.
	• Interrupted – integration works only partially:		* '''Interrupted''' – integration works only partially:
	** At least one file transferred successfully AND at least one file failed.		** At least one file transferred successfully AND at least one file failed.
	** New files are processed.		** New files are processed.
	** Failed files remain as "Failed" until a successful retry.		** Failed files remain as "Failed" until a successful retry.
	** '''The user can try to fix the connection and manually retry the connection'''.		** '''The user can try to fix the connection and manually retry the connection'''.
	• Failed – integration has failed:		* '''Failed''' – integration has failed:
	** One or more file transfers have failed AND no file transfer has been successful:		** One or more file transfers have failed AND no file transfer has been successful:
	*** New files are processed.		*** New files are processed.
Line 61:		Line 61:
	*** Integration is skipped when files are queued, no uploads are attempted.		*** Integration is skipped when files are queued, no uploads are attempted.
	** '''The user can try to fix the connection and manually retry the connection'''.		** '''The user can try to fix the connection and manually retry the connection'''.

	===SFTP Server Settings===		===SFTP Server Settings===
	[[File:TachoSync Integrations settings.png\|thumb\|right\|alt=TachoSync Integrations settings\|TachoSync SFTP integration settings]]		[[File:TachoSync Integrations settings.png\|thumb\|right\|alt=TachoSync Integrations settings\|TachoSync SFTP integration settings]]