Configuration (Import)

On the import definition there are some general settings, these are described in this section. There are also specific settings per file and method, these are describe in the data formats and methods.

General tab

On the General tab, give the definition a recognizable description. Select the data format of the incoming data and select the method that will be used.

Supported data formats currently are JSON, XML, CSV and Excel.
Currently supported import methods are Manually, FTP, REST, SOAP, Azure Storage, Azure Service Bus, Dropbox REST Endpoint and Intercompany.
It is possible to use configuration templates during import. For more information on how to set this up, see the Configuration Templates section.
If the record driven option is on, it will be always imported record by record
The active option is used for the license, only active defintions will be calculated for the limited licenses.
The option example is used by idyn to preinstall example definitions where you can filter on in the menu.

Processing rules tab

The tab processing rules is used to set the maximum number of retry attempts, when an import runs into an error. In the general settings, there is a default set for all definitions and in this tab you can change this for this specific definition.

Flow tasks tab

In the tab Flow tasks a automated flow can be set. Before, after and/or during importing a record, tasks can be executed for example to reopen and afterwards post a document. You can use any codeunit available in BC to add as a flow task and it is also possible to combine multiple codeunits in one task.

For more information on pre- and post processing tasks, see the Tasks section.

Recurrense tab

In the recurrence tab it is possible to run a recurring job to import the data, you can set per day/ time and numbers of minutes between the runs. This recurrence job uses at the back ground the standard Job queue. In the last run you can see when the job queue has ran. More about this topic , is on this page: Scheduling

Example how start / end dates work at the import side:

If you use a start and ending time, please make sure the number of minutes between a run will be in the start and ending time.

For example what works:

the starting time is on 00:00:00
the ending time is on 01:00:00
the number of minutes is between runs = 5
the last run was on 00:55:00 8-5-2026
The outcome: the next day (9-5-2026) 5 it will run 00:00:00 because it is set on 5 minutes, it will start on the first starting time the next day.

For example what doens’t work:

the starting time is on 00:00:00
the ending time is on 01:00:00
the number of minutes is between runs = 1440
the last run was on 01:00:00 8-5-2026
The outcome: the next day (9-5-2026) 1440 minutes later it will run 01:00:00 but this will be on the ending time.

It is also possible to activate an Advanced Schedule to set up a cycle with a date formular or with in anterval of minutes, hours, days, weeks, months.

Definitions lines tab

In the tab definition lines, you can setup the mapping. In this page more about this: Definition Lines (Import)

Constant values tab

In the tab Constant values, you can set up variables that BC needs to import the data in the right format to create a record. In the following page more about this: Constant Values

Alerts tab
For more information on Alerts, see the Alert notification page.

Logging tab

For more information on logging, see the Logging page. If you don’t change the setting on the definition card the settings from the general settings will be used.

Projects tab

For more information on projects, see theProjects page