Upon installing the application, you will find two main menus: one for server configuration and the other for import/export configuration.

You can configure the FTP server under the FTP Syncing menu.

You can configure the SFTP server under the SFTP Syncing menu.

Configuration of mapping table:

Name: You need to give the name for the configuration table.

Mapping Model: You need to select the model from which you want to export the records.

Type: This field specifies the type of operation the configuration table is intended for—whether it will be used for import or export.

Main Table: You need to enable this option if your configuration is main. For example if you want to add a sale order record then for the sale order model you need to create configuration record with main table enable & you need to create sale order line configuration separately without main table enable.

Company: Reference of company.

Partner: Reference of Partner/Contact – this is for your reference in case you have created multiple export mapping configurations, allowing you to easily identify which configuration belongs to which partner.

Enter Export File Name: You can specify the file name that will be used for the exported file.

Export File Type: You need to select the file type or format from the available options: CSV, TSV, or XLSX.

Enter Filter (Domain): If you need to export specific records from the selected mapping model, you can define a filter/domain here.

Select Upload Option: You need to select the method how you want to export the file.

Server Type: You need to select the server type to which the file for this configuration will be exported.

Select FTP/SFTP: You need to select the corresponding FTP or SFTP server configuration record.

File Path: You need to enter the destination file path where the file should be stored on your FTP/SFTP server.

Select partners to send created file in mail: You need to select the partners whom you want to send the created file via mail.

Model Fields:

Selected Model Fields: You can select the fields from the chosen model that you want to include in the exported file.

Field to search for M2O: This field is optional. If you select a Many2one field for mapping, you can specify a sub-field from the related model to export its specific value. If not specified, the default name field of the Many2one model will be used.

Field to search for M2M: This field is optional. If you select a Many2many field for mapping, you can specify a sub-field from the related model to export its specific value. If not specified, the default name field of the Many2many model will be used.

Required: You can enable this option if the field's value must not be empty. If it is marked as required and found empty, the file will not be generated.

Sub Table for Relational Field: For a One2many mapping field, you need to select a sub-table where a separate configuration is defined for the One2many field's model. The same concept is followed in the sub-table configuration, with the only difference being that you do not need to enable the Main Table option there.

This is a sub-table configuration where you need to specify the name, model and type; selecting the main table is not required. Below are the mapping fields for the selected model (as explained in the previous step).

These scheduled actions are responsible for preparing the file and exporting it to the designated server.

The initial scheduled action is responsible for generating the file to be exported.

Upon running the scheduled action, new transaction records will be generated under the Export Transactions menu.

After the file is successfully generated, it will be available within the corresponding transaction record along with the generated file.

If any field marked as required is left empty during export, the file generation will be halted to prevent incomplete data from being exported.

A transaction will be created in a failed state, and you will see a new button to re-generate the file along with log details explaining why the file was not generated.

You can review the log details directly from the transaction. In this case, the file generation failed because a required field was left empty.

Once you rectify the error—by providing the missing value for the required field in the specific record—you can click the *Re-compute* button. This will regenerate the file, and the transaction will move to the *draft* state, indicating it is now ready for export.

This is the second scheduled action, responsible for exporting files that are in the Draft state to the configured server.

You can check the transaction state as Done once the file has been successfully exported to the server, along with the corresponding log details.

You can view the detailed logs directly from the transaction record and also from the FTP/SFTP Syncing menu.

You have to set up an outgoing mail server to automatically send generated file via mail.

Generated files will be automatically sent to the partners selected in mapping table.

You have to set the email inside that partner to successfully send the file via mail.

If email is not set in any selected pertner then transaction state will be set to Not Sent. You can set the state to draft from **Reset to Draft** button after reviewing the logs.

You can view the related logs directly from the transaction record. In this case, emails were not found for any selected partner.

After making the necessary changes, you can see the transaction is done.

You can view the detailed logs directly from the transaction record. If in case, some partner have email set on them and some does not, we send the file to the partners with email.

This is the SFTP server to which the file has been successfully exported.

This is an example of the file that has been successfully exported.