Commit Task

Note: Not all datastores support the Commit task, see Data Stores.

A Commit task is used to write back data to a data store that has already been opened using an Open Data task.

There must be an Open Data task in the session before you add a Commit task.

Note: If you update the data store used in your Open Data task, it will automatically update your Commit task.

Commit writes back data using the input mapping defined in the data store (see Input Mapping). Only a subset of changed data is written back to the data store.

Note: If you want to write data back to a different data store then you will need to use a Copy To task (see Copy To Task).

ClosedPrimary Keys

1Integrate needs to be able to identify records to update in a database. In order for 1Integrate to find these records, a primary key restraint must be present. Please refer to the relevant database documentation.

Note: For PostGIS updates, you must have a numerically typed primary key.

ClosedAdd a Commit task to a Session

  1. Navigate to the Sessions workspace.

  2. From the Navigation Pane, select a session to edit.

  3. Open the Tasks tab.

  4. Click New and select Commit.

  5. In the Select dialogue that appears, select the data store to be used.

  6. Click OK.

  7. Click Save.

Commit Task Results

Once a session is run, a completed Commit task provides an XML file detailing the number of objects committed and the number of errors, in summary and for each class.