Import Scheduler

\# written by viktor linde | last published at december 15, 2025 \# # introduction the enapps erp system supports importing data from both ftp/sftp servers and external sql databases using the built in import scheduler functionality the import scheduler allows the execution of both file based and database based imports through configurable import chains within the erp these chains define the sequence and logic of how data is received, processed, and integrated into the system to enable full automation, the import scheduler can be linked to a scheduled action, allowing imports to run at scheduled intervals without manual intervention \# ftp/sftp configuration you can set up a connection to ftp and sftp servers the choice of the desired protocol depends on your infrastructure and security requirements 1\ go to settings > import and export tools > configs > ftp configuration 2\ fill in the following fields field description host the server address (e g , ftp example com) port the port number (commonly 21 for ftp and 22 for sftp) username the login username for the server password the associated password for authentication use sftp tick the checkbox to use sftp protocol when unchecked \# ftp configuration options when using ftp, users have access to several additional configuration options these options are specific to ftp due to how the protocol is structured and do not apply to sftp field description ssl/tls enables encryption over standard ftp, securing credentials and data during transfer passive mode helps bypass firewall restrictions by allowing the client to initiate both control and data connections this is especially useful in environments with strict outbound firewall rules command timeout defines a time limit for ftp commands this prevents the system from hanging indefinitely if the server becomes unresponsive \# import scheduler with ftp set up when using the ftp import option, define the folder paths for the following field description folder for new files the directory from which the system reads incoming files to be imported folder for processed files the directory where files are moved after being successfully imported folder for failed files the directory for files that could not be processed due to errors it is important to ensure these folders are accessible and correctly specified within the ftp configuration to ensure smooth import operations in case of errors during import, the system will log the issue in the import scheduler log, displaying the file name and corresponding error message for easier troubleshooting the file import will then run through the import chain linked in the import chain field \# importing from external databases the enapps erp supports setting up the import scheduler for importing from the following types of sql databases postgresql mysql microsoft sql details for db are required to be entered as follows external database connections within the enapps erp system require the following configuration parameters host, port, database, username, and password these details must be correctly entered to establish a connection \# import scheduler with database set up when selecting the "database" option in the import scheduler, the user must provide both the database connection details and the sql query to execute the result of this query is treated as if it were a csv file, meaning that only csv based imports are supported in this configuration to ensure successful data mapping, the structure of the query result must either match the exact sequence of fields defined in the import chain, or include headers that correspond to the field names, if using a header based import setup proper alignment between the query output and the import chain configuration is essential for accurate data processing \# connecting import schedulers to scheduled actions an import scheduler is commonly connected to a scheduled action, which enables automated execution at defined time intervals this is the standard approach for automating recurring data import tasks within the enapps erp system typical use cases include automated sales order imports purchase order processing invoicing automation to configure this correctly, the id of the import scheduler (found in the bottom right corner of the import scheduler screen) should be copied and inserted into the arguments field of the scheduled action in the following format (\[\<import scheduler id>],) refer to the example below for proper scheduled action setup the above screenshot is part of a standard scheduled action set up for import schedulers users may duplicate this scheduled action and modify the arguments field for specific scheduled actions