Skip to main content

FTP - Connector settings

FTP - Connector Settings This document describes the connector-specific settings for the FTP connector. These settings influence various...

Updated over a week ago

FTP - Connector Settings

This document describes the connector-specific settings for the FTP connector. These settings influence various aspects of the connector's behavior, including data transfer security, item synchronization logic, file naming conventions, and data formatting. Administrators can configure these settings to ensure proper integration with external systems.

Settings are typically stored via the App4Sales portal UI or through XML configuration files and are applied at runtime when the connector performs its operations.

Setting

Description

Values / Defaults

Dependencies / Effects

Use SFTP

Determines whether the connector uses Secure File Transfer Protocol (SFTP) for secure data transfer over SSH.

Boolean (true/false). Defaults to false.

Enabling this requires the FTP server to support SFTP. Mutually exclusive with TLS and SSL settings for the same connection.

Use CSV item sync logic

If enabled, the connector will utilize specific logic tailored for synchronizing item data from CSV files.

Boolean (true/false). Defaults to false.

Affects how item data is parsed and processed from CSV inputs. Ensure your CSV files are structured according to the expected format for this logic.

Use source prefix on orderfiles

When enabled, a predefined source prefix will be added to the filenames of order files transmitted by the connector.

Boolean (true/false). Defaults to false.

Influences the naming convention of output order files, which can be useful for identification or routing on the receiving system.

Replace linefeeds with

Specifies a custom character or string to replace all line feed characters (\n) found within the data content before it is transferred.

String. Can be any character sequence. Defaults to an empty string (no replacement).

Useful for ensuring data compatibility with target systems that handle line feeds differently or expect a flat file format.

Encrypt FTP data using TLS

Determines whether the connector uses Transport Layer Security (TLS) to encrypt the FTP data transfer.

Boolean (true/false). Defaults to false.

Requires the FTP server to support TLS encryption. Mutually exclusive with SFTP and SSL settings for the same connection.

Encrypt FTP data using SSL

Determines whether the connector uses Secure Sockets Layer (SSL) to encrypt the FTP data transfer.

Boolean (true/false). Defaults to false.

Requires the FTP server to support SSL encryption. Mutually exclusive with SFTP and TLS settings for the same connection.

Remove semi colon at the end

If enabled, the connector will remove any trailing semicolons from lines of data before transferring them.

Boolean (true/false). Defaults to false.

Aids in data cleanup and can prevent parsing errors in target systems that do not expect trailing semicolons.

SendCustomerToFtp

Controls whether customer data is included in transfers to the FTP server. This setting is primarily to prevent errors in scenarios where the FTP server might not have a dedicated 'Customers' folder.

Boolean (true/false). Defaults to false.

Disabling this can prevent transfer errors if the FTP destination is not configured to receive customer data, but it also means customer data will not be synchronized.

Domain Specifics

Security

The connector offers multiple options for securing data transfer: Use SFTP, Encrypt FTP data using TLS, and Encrypt FTP data using SSL. Only one of these secure transfer methods should be enabled at a time, depending on the capabilities and configuration of the external FTP server. Enabling multiple options simultaneously may lead to connection issues.

Data Formatting

Settings like Replace linefeeds with and Remove semi colon at the end provide control over the data format sent to the FTP server. These are crucial for ensuring that the transmitted files are correctly parsed and processed by the receiving system, especially when dealing with strict format requirements or legacy systems.

Did this answer your question?