/visma-net-erp/help/integration/configuring-import-scenarios section You create import scenarios in the Manage import scenarios (SM206025) window. 2026-02-19T17:09:06+01:00 # Configuring import scenarios You create import scenarios in the Manage import scenarios (SM206025) window. For more information: [Manage import scenarios (SM206025)](/visma-net-erp/help/integration/integration-windows/manage-import-scenarios-sm206025/). To create an import scenario, you should specify its name, the Visma Net window that should be used for importing data, the data provider that defines the structure of the imported data, and the data provider object. You should also configure the mapping of the scenario. /visma-net-erp/help/integration/configuring-import-scenarios/import-scenario-creation page You create import scenarios in the Manage import scenarios (SM206025) window. 2026-02-19T17:09:06+01:00 # Import scenario creation You create import scenarios in the Manage import scenarios (SM206025) window. For more information: [Manage import scenarios (SM206025)](/visma-net-erp/help/integration/integration-windows/manage-import-scenarios-sm206025/). The creation of the import scenario consists of the following general steps: ## 1. Analysing the sequence of actions in the window Before you start creating an import scenario in the [Manage import scenarios (SM206025)](/visma-net-erp/help/integration/integration-windows/manage-import-scenarios-sm206025/) window, you should create a data provider, as described in [About data providers](/visma-net-erp/help/integration/preparing-data-for-import-and-export-by-using-scenarios/about-data-providers/), and learn how a data record is entered in the target Visma Net window. When reviewing the Visma Net window for which you will compose the import scenario, pay attention to the required fields in the window. All these fields must be filled in when you create a new record. Some fields in the window can get default values, which can also be used during import. For example: You can configure customer classes before you import customer records so that when these records are imported, the system gets most of settings from the customer class specified for the customer. You can provide the values of the fields that have default values during import and override these default values. Make sure all required data fields either are included in the imported data or are filled with default values. Before you start creating a scenario, we strongly recommend that you manually enter one record of the imported data or a test record. (During import, you can exclude this record from processing to avoid duplication of records in the system). Pay attention to the sequence of actions you perform: the order in which you specify values in the fields in the window and the actions you perform for the entered record, such as adding a new row and saving your changes. ## 2. Specifying scenario parameters The parameters of an import scenario define the name of the scenario, the Visma Net window to which data will be imported, and the data provider and source object, which together specify the data source. You can also set other import scenario parameters that define the mode of import and the properties of the data being imported. ## 3. Creating mapping of the scenario Mapping is the process of creating one-way relations between the fields of an external data source and the fields of a Visma Net window. To provide mapping for a particular field in a Visma Net window, you perform the following steps on the **Mapping** tab of the [Manage import scenarios (SM206025)](/visma-net-erp/help/integration/integration-windows/manage-import-scenarios-sm206025/) window: 1. Add a row for the field you want to map. 1. In the **Target object** column, specify the Visma Net object that includes the target field. An object represents a group of fields in a Visma Net window, such as the top part or a detail tab. 1. In the **Field/action name** column, select the appropriate internal field or action. An internal field is a field of the Visma Net object selected in the **Target object** column. 1. In the **Source field/value** column, select the matching external field, internal field, or combination of internal and external fields, functions, and constants. An external field is a field of the object from the data provider specified in the scenario. When you are mapping fields, you should first map the key fields: the fields that the system uses to distinguish records that belong to different documents. For example: In the [Sales invoices (AR301000)](/visma-net-erp/help/customer-ledger/customer-ledger-windows/sales-invoices-ar301000/) window, there are two key fields: **Type** and **Reference no**. You should map these fields before you map the other fields, because you fill in these fields first on the window when you manually enter an invoice. After you have mapped key fields, you should map other fields in the order in which you would fill them in, in the window. You can deactivate some rows of the scenario mapping by clearing the **Active** check box for corresponding rows. This will exclude the corresponding instruction from the scenario mapping, and this instruction will not be executed during the import process. At the end of the mapping of the scenario that imports or updates data in the system, to save the imported record to the database, you have to insert a row with the **<Action: Save>** action. ## 4. Configuring source and target restrictions To import only some records from the data source or update only the records that satisfy some condition, you can configure source and target restrictions for an import scenario in the [Manage import scenarios (SM206025)](/visma-net-erp/help/integration/integration-windows/manage-import-scenarios-sm206025/) window. You can find detailed descriptions and examples of the use of source and target restrictions in the following topics: + [Source restrictions in import scenarios](/visma-net-erp/help/integration/configuring-import-scenarios/source-restrictions-in-import-scenarios/) + [Target restrictions in import scenarios](/visma-net-erp/help/integration/configuring-import-scenarios/target-restrictions-in-import-scenarios/) After these steps have been performed, the scenario is ready, and you can use it for data processing. /visma-net-erp/help/integration/configuring-import-scenarios/import-scenario-parameters page When you begin creating an import scenario by using the Manage import scenarios (SM206025) window, you specify the following required parameters: 2026-02-19T17:09:06+01:00 # Import scenario parameters When you begin creating an import scenario by using the Manage import scenarios (SM206025) window, you specify the following required parameters: For more information: [Manage import scenarios (SM206025)](/visma-net-erp/help/integration/integration-windows/manage-import-scenarios-sm206025/). Name : In this field, you specify a name that reflects the functionality of the import scenario. You have to use unique names between import and export scenarios. Window name : In this field you select the Visma Net window that should be used for data import. Provider : and **Provider object**: In these fields, you select one of the previously created data providers and its object that should be used for data import. If you select a file data provider, Visma Net automatically attaches to the scenario in the [Manage import scenarios (SM206025)](/visma-net-erp/help/integration/integration-windows/manage-import-scenarios-sm206025/) window the file used for file data provider creation. This file is shared between the data provider and the import scenario that uses it for data import or it is attached to both the [Data providers - reference information](/visma-net-erp/help/integration/integration-windows/data-providers-sm206015/) window for the provider and the [Manage import scenarios (SM206025)](/visma-net-erp/help/integration/integration-windows/manage-import-scenarios-sm206025/) window for the scenario. You can view and modify the attached file in the [File maintenance (SM202510)](/visma-net-erp/help/management/management-windows/file-maintenance-sm202510/) window; to open the window, while you are viewing the import scenario, click **Files** in the title bar. After you specify the required parameters, you can set the following optional parameters: + **Sync type**: By default, the **Full** sync type is selected in this field, which means that all data available in the source is imported. Selecting a different option is useful if you use the same scenario regularly for importing only some of the data from the source. For example: If after the initial import you need to periodically upload new data records that have appeared in the source. If the data is imported from a file data source, you can set the scenario to import the data only if a new version of the source file is provided before import. To do this, set **Sync type** to **Incremental - All records** or **Incremental - New only**; both options provide the same result. In this case, if you upload a new version of the source file by using the [Import by scenario (SM206036)](/visma-net-erp/help/integration/integration-windows/import-by-scenario-sm206036/) window before import, the data from the source file is imported to the system. If no new version of the file is provided, no data is imported. + **Format locale**: For Visma Net to recognise the format of imported dates, numbers, and other country-specific data correctly, you should specify the appropriate locale in this field. By default, Visma Net uses the invariant locale, which is similar to the English (United States) locale. The newly created scenario has the **Active** check box selected by default. This check box must be selected so that you can use the scenario for processing records in the [Import by scenario (SM206036)](/visma-net-erp/help/integration/integration-windows/import-by-scenario-sm206036/) window. /visma-net-erp/help/integration/configuring-import-scenarios/target-objects-and-fields-in-import-scenarios page When you are performing mapping on the Mapping tab of the Manage import scenarios (SM206025) window, you have to select the target object and field. 2026-02-19T17:09:06+01:00 # Target objects and fields in import scenarios When you are performing mapping on the Mapping tab of the Manage import scenarios (SM206025) window, you have to select the target object and field. For more information: [Manage import scenarios (SM206025)](/visma-net-erp/help/integration/integration-windows/manage-import-scenarios-sm206025/). ## The target objects and fields In the **Target object**column, you have to select the object of the Visma Net window into which you want to insert the value. The object names that appear in this drop-down field are the names of the UI elements that you see in the window. Custom UI elements that you add to the system by means of customisation are also available for mapping in the same way as the original ones. For example, to be able to select the **Statement cycle ID** field that is located in the **Financial settings** group on the **General info** tab of the [Customers (AR303000)](/visma-net-erp/help/customer-ledger/customer-ledger-windows/customers-ar303000/) window, you would select `General info -> Financial settings` as the target object for mapping. Each field or action on a Visma Net window (such as a text box, combo box, table column, or button) is associated with a particular target object and becomes available for selection in the **Field/action name** column once you select the target object in the **Target object** column. The field name has the same name as the corresponding field in the window, such as `Statement cycle ID`. If you are not sure that you have selected the field name correctly, you can check it as follows: 1. On the **Mapping** tab of the [Manage import scenarios (SM206025)](/visma-net-erp/help/integration/integration-windows/manage-import-scenarios-sm206025/) window, add the **Native field/Action name** column to the mapping table. (You can change the list of columns that are displayed in the mapping table in the **Columns configuration** dialog box, which opens if you click the header icon of the first column in the mapping table.) In the **Native field/Action name** column, you can see the internal name of the target field. 1. In the title bar of the target Visma Net window, click **Customisation** **>** **Inspect element** and click the target element in the window. In the **Element properties** dialog box, which opens, check that the value of the **Data field** element is equal to the value in the **Native field/Action name** column in the mapping table in the [Manage import scenarios (SM206025)](/visma-net-erp/help/integration/integration-windows/manage-import-scenarios-sm206025/) window. Multiple objects support the functionality of each Visma Net window: a summary object, detail objects, and related objects. These types of objects are described in the following sections. ## The summary object The summary object is the main object in the window; it contains the keys that identify the record in the system. You can use the fields of the summary object to do the following: + Set the values of the corresponding fields in the window. + Search for a record in the system. That is, you can create custom keys from these fields to search for a particular record. For example: You can find a needed customer record in the system by using the value of the **Customer name** field in the [Customers (AR303000)](/visma-net-erp/help/customer-ledger/customer-ledger-windows/customers-ar303000/) window. + Filter imported records by these fields by using target restrictions. For example: You can select for processing only the customer records that have the **Inactive** status in the **Status** field in the [Customers (AR303000)](/visma-net-erp/help/customer-ledger/customer-ledger-windows/customers-ar303000/) window. Generally, you can identify the fields that belong to the summary object in the window as the fields of the top part of the window. More precisely, these are the data fields of the data access class (DAC) underlying the summary object. To use the summary object in scenario mapping, select the first object in the **Target object** drop-down field on the **Mapping** tab of the [Manage import scenarios (SM206025)](/visma-net-erp/help/integration/integration-windows/manage-import-scenarios-sm206025/) window. For example: The summary object in the [Customers (AR303000)](/visma-net-erp/help/customer-ledger/customer-ledger-windows/customers-ar303000/) window is `Customer summary`. It includes the key **Customer no.** field. The summary object in the [Sales invoices (AR301000)](/visma-net-erp/help/customer-ledger/customer-ledger-windows/sales-invoices-ar301000/) window is `Invoice summary`. It includes two key fields: **Type** and **Reference no**. ## The detail objects Detail objects correspond to the tabs that include lists of detail records. The fields of a detail object correspond to the columns of the detail tab. You can use the fields of the detail object to do the following: + Set the values of corresponding fields of a detail line. + Search for a detail line in the document. That is, you can create custom keys from these fields to search for a particular detail line in the document. For example: In the [Sales invoices (AR301000)](/visma-net-erp/help/customer-ledger/customer-ledger-windows/sales-invoices-ar301000/) window, you can find a needed detail line of a sales invoice by using the value in the **Transaction descr.** column. To use the detail object in the scenario mapping, in the **Target object** column in the **Mapping** tab of the [Manage import scenarios (SM206025)](/visma-net-erp/help/integration/integration-windows/manage-import-scenarios-sm206025/) window, select the object with the same name as the name of the detail tab. For example, [Customers (AR303000)](/visma-net-erp/help/customer-ledger/customer-ledger-windows/customers-ar303000/) window has the **Contacts** tab, shown in the following screenshot, which includes a list of contacts. The corresponding detail object has the `Contacts` name. In the [Sales invoices (AR301000)](/visma-net-erp/help/customer-ledger/customer-ledger-windows/sales-invoices-ar301000/) window, the `Document details` object contains a list of invoice lines. ## The related objects Related objects support the functionality of other tabs and groups of fields in the window. You can use the fields of these objects only to set the values of the corresponding fields in the window. You cannot use the fields of these objects to search for records by using customer keys or to filter imported records by using target restrictions. For example: In the [Customers (AR303000)](/visma-net-erp/help/customer-ledger/customer-ledger-windows/customers-ar303000/) window, you cannot search for the needed customer record by using the value of the **Email** field of the **Main contact** group of the **General info** tab as a custom key, and you cannot filter records by using the **Country** field of the **Main address** group of the **General settings** tab by using target restrictions. To use a related object in the scenario mapping, in the **Target object** column in the **Mapping** tab of the [Manage import scenarios (SM206025)](/visma-net-erp/help/integration/integration-windows/manage-import-scenarios-sm206025/) window, select the object with the name of corresponding tab or group of fields in the window. The related objects that correspond to tabs in the window have the names of the tabs. The related objects that correspond to groups of fields in the window have names in one of the following formats: `Summary name -> Group of fields name` or `Tab name -> Group of fields name`. For example, in the [Customers (AR303000)](/visma-net-erp/help/customer-ledger/customer-ledger-windows/customers-ar303000/) window, the **Main contact** and **Main address** groups of elements on the **General settings** tab are represented by related objects. These objects are listed in the **Target object** column as `General info -> Main contact` and `General info -> Main address`. /visma-net-erp/help/integration/configuring-import-scenarios/source-fields-in-import-scenarios page When you are performing mapping on the Mapping tab of the Manage import scenarios (SM206025) window, you have to select in the Source field / value column the source field from which the system takes the value to be inserted into the target field. 2026-02-19T17:09:06+01:00 # Source fields in import scenarios When you are performing mapping on the Mapping tab of the Manage import scenarios (SM206025) window, you have to select in the Source field / value column the source field from which the system takes the value to be inserted into the target field. For more information: [Manage import scenarios (SM206025)](/visma-net-erp/help/integration/integration-windows/manage-import-scenarios-sm206025/). You can use the following as source fields: + The fields defined in the data provider + The fields of a Visma Net window, from which we can take the value that already exists in the system or the default value + Any combination of the fields defined in the data provider, the fields of a Visma Net window, constants, and functions ## Relationships between source fields and target objects and fields Source data includes a set of master records, such as customer account records. Each master record has a set of fields that are mapped to the fields of the summary object and related objects. For customer accounts, these fields can include **Customer number** and **Email**. There may be only one value of such field for each summary object or related object. A master record can have a set of detail lines that are mapped to the fields of detail objects. For example, a customer account can have multiple contact details. There may be many detail lines for each detail object. Therefore, for these detail lines to be imported to Visma Net, external data should include the identifier of the master record for each detail line. That is, each detail line should have the key fields of the summary object specified. For example, suppose that you have a customer account with two contact details. In this case, the external data that you are going to import to Visma Net should include two records, one record with the customer number and contact information for each contact detail. Such records should include a key field that the system uses to distinguish lines that belong to different records. /visma-net-erp/help/integration/configuring-import-scenarios/source-restrictions-in-import-scenarios page You can use source restrictions to filter the data that you want to extract from the source for processing by the import scenario. 2026-02-19T17:09:06+01:00 # Source restrictions in import scenarios You can use source restrictions to filter the data that you want to extract from the source for processing by the import scenario. You can use source restrictions to filter the data that you want to extract from the source for processing by the import scenario. For example: Some customer number values in the source have **CUST** prefixes. You can specify a source restriction that selects only the records from the source that have the **CUST** prefix in the customer number field. To configure restrictions on the data that will be extracted from the source during the import, you specify conditions for the fields of the source file on the **Source restrictions** tab of the [Manage import scenarios (SM206025)](/visma-net-erp/help/integration/integration-windows/manage-import-scenarios-sm206025/) window. If you specify source restrictions, when the system prepares records for import, it selects only the records that conform to the specified condition or conditions from the source and imports only these records. For example, suppose that you want to import only the customer records that have the **CUST** prefix in the customer number. In this case, you can add the condition to the source restrictions that the external customer number field should start with the **CUST** prefix. The system will import only the records for which the customer number has the specified prefix. /visma-net-erp/help/integration/configuring-import-scenarios/target-restrictions-in-import-scenarios page You can specify target restrictions that apply to records after they have been processed by the import scenario. 2026-02-19T17:09:06+01:00 # Target restrictions in import scenarios You can specify target restrictions that apply to records after they have been processed by the import scenario. You can specify target restrictions that apply to records after they have been processed by the import scenario. For example: Suppose that you have imported customer records to Visma Net and then manually changed the status of some of these records to **Inactive** in the [Customers (AR303000)](/visma-net-erp/help/customer-ledger/customer-ledger-windows/customers-ar303000/) window, and now you want to update only imported customer records that have the **Inactive** status. Because you do not have the status in the source file, you cannot use source restrictions to select needed records. You can, however, specify a target restriction that makes the system save the results of import for only the records that have **Inactive** status in the window. To configure restrictions that apply to records after they have been processed by the import scenario, you specify conditions for the target fields on the **Target restrictions** tab of the [Manage import scenarios (SM206025)](/visma-net-erp/help/integration/integration-windows/manage-import-scenarios-sm206025/) window. If you have specified target restrictions, after a record is imported, the system checks the conditions for the imported record. If a record meets the conditions, the system saves the result of processing the record during import. If a record violates the target restrictions, the resulting record is not saved; by default, the system stops processing records and displays an error. To make the system skip errors for the records that do not meet the restrictions and proceed with processing other records, you should set the system to not break on an incorrect target. In this case, the system will continue to process subsequent records after an error has occurred for a record. For example, suppose that you want to delete customer records that have an **Inactive** status in the [Customers (AR303000)](/visma-net-erp/help/customer-ledger/customer-ledger-windows/customers-ar303000/) window. To do this, you can add to the target restrictions the condition that the imported customer records should have the **Inactive** status. During import, the system will check whether each imported record has the **Inactive** status, and delete the record only if it has this status. To determine target restrictions, you can use only the fields of the summary object. For example: In the [Customers (AR303000)](/visma-net-erp/help/customer-ledger/customer-ledger-windows/customers-ar303000/) window, you can filter records by the **Customer number**, **Customer name**, and **Status** fields. You cannot use columns of **Select** dialog boxes, fields of related objects, and fields of detail objects to filter records. For example: For this window, you can filter customer records neither by the value of the **Country** field of the **Main contact** group on the **General settings** tab, nor by the **Country** column of the Selector dialog box of the **Customer no.** field. /visma-net-erp/help/integration/configuring-import-scenarios/enable-manual-override-of-number-series-during-import section Import is normally run from the Import by scenario (SM206036) window. 2026-02-19T17:09:06+01:00 # Enable manual override of number series during import Import is normally run from the Import by scenario (SM206036) window. For more information: [Import by scenario (SM206036)](/visma-net-erp/help/integration/integration-windows/import-by-scenario-sm206036/). If you need to do a manual override of the number series during the import, you can enable this by following the steps below. 1. Go to the [Enable/disable functionalities (CS100000)](/visma-net-erp/help/common-settings/enable-or-disable-functionalites/enable-disable-functionalities-cs100000/) window. 1. Select the **Allow manual numbering on imports** check box. 1. Click . 1. Go to the [Manage import scenarios (SM206025)](/visma-net-erp/help/integration/integration-windows/manage-import-scenarios-sm206025/) window. 1. Select the **Override number series upon import** check box. 1. Click .