---
title: "Fields with commit in import and export scenarios"
description: "There are two types of fields in Visma Net windows: fields with commit, and fields without commit."
lang: en
languages:
  en: https://docs.vismasoftware.no/visma-net-erp/help/integration/configuring-scenario-mapping/fields-with-commit-in-import-and-export-scenarios/index.md
lastmod: 2026-02-19
---

> Documentation index: https://docs.vismasoftware.no/visma-net-erp/help/integration/configuring-scenario-mapping/llms.txt


# Fields with commit in import and export scenarios

Last modified February 19, 2026

> There are two types of fields in Visma Net windows: fields with commit, and fields without commit.


There are two types of fields in Visma Net windows: fields with commit, and fields without commit.
A commit is an action initiated
by the window that, when triggered, sends the data to the server.
On the server, the
commit causes all data in the window to be updated, including the insertion of default
values and the recalculation of appropriate fields in the window.

A commit is a costly operation that causes the browser to make requests to the server and takes
server time.
As such, a commit is invoked for only a limited number of fields: mainly
the key fields and the fields on which the other fields depend.
On the
**Mapping** tab of the
[Manage import scenarios (SM206025)](https://docs.vismasoftware.no/visma-net-erp/help/integration/integration-windows/manage-import-scenarios-sm206025/index.md) window or the [Manage export scenarios (SM207025)](https://docs.vismasoftware.no/visma-net-erp/help/integration/integration-windows/manage-export-scenarios-sm207025/index.md) window,
if you select a field for which the system performs a commit, the system automatically
selects the **Commit** check box.

If the **Commit** check box is cleared on this tab, the field is filled in
with data, but no update of the window is invoked.
If the **Commit**
check box is selected, after the field is filled in, the commit is invoked on the server
and the window is updated.

For example: When you select a customer in the [Sales invoices (AR301000)](https://docs.vismasoftware.no/visma-net-erp/help/customer-ledger/customer-ledger-windows/sales-invoices-ar301000/index.md) window, the system assigns values to fields related to customer settings, such as the customer terms, due date, and cash discount date. When you create an import scenario for this window, for fields such as **Customer**, the system automatically selects the **Commit** check box on the **Mapping** tab of the [Manage import scenarios (SM206025)](https://docs.vismasoftware.no/visma-net-erp/help/integration/integration-windows/manage-import-scenarios-sm206025/index.md) window.

In most cases, when you compose the mapping of an import or export scenario, you can use the
**Commit** check boxes as they are set by default.
However, you
may need to force the system to invoke a commit to the server, for example, when you need
to commit the value of one field before entering another field value, or to indicate the
beginning and the end of a record if you enter records without specifying the key field
value.
In such cases, you should manually select the **Commit** check
box for the field or action.

Parent topic:

[Configuring scenario mapping](https://docs.vismasoftware.no/visma-net-erp/help/integration/configuring-scenario-mapping/configuring-scenario-mapping/index.md)


---

[View this page](https://docs.vismasoftware.no/visma-net-erp/help/integration/configuring-scenario-mapping/fields-with-commit-in-import-and-export-scenarios/)