Push Connector > Options Tab

This describes the operation of the different fields of Options tab of the push connector.

ERP System

Select the system into which the transactions are to be imported. The systems are defined in the Setup Items area.

Where a connector supports SYS.SYSCONNECTID field to dynamically target the system to push the transactions, the ERP System drop down on the options tab determines system the connector will connect to obtain any system specific meta-data.

Import Type

The Import Type field specifies the transaction or master data type that is being imported with. In the example above the transform is setup to import O/E Orders.

This list will be populated with either a static list of supported 'imports' or dynamically populated based on the application's metadata.

Once the transform is configured, this cannot be altered.

Update Operation

Specifies how data should be inserted or updated within the application.

Natural Key

On imports which supporting different update operations a check is typically made by the connector to determine whether an existing record is updated or deleted or a new record inserted. The check is performed using the natural key of the data being imported. The natural key is typically the identifier used to retrieve the record or data within the application itself. E.g. The customer number when retrieving a sales ledger or A/R customer, the document number when retrieving any transaction.

On imports which support different update operations a check is typically made by the connector to determine whether an existing record should be updated/deleted or a new record inserted. The check is performed using the natural key of the data being imported.

The natural key is typically the identifier used to retrieve the record or data within the application itself. E.g. The customer number when retrieving a sales ledger or A/R customer, the document number when retrieving any transaction.

See the relevant Connector guide for more information on Natural Key.

Insert Only

Only new data will be inserted into the application. On imports supporting more than just insert the following strategy is used to determine if a record is inserted:

  • If the natural key of the import type is either not mapped or empty a new record is inserted.
  • If the natural key of the import type is mapped and there exists a matching a transaction or record within the application the record from IMan will be skipped and therefore not created.
  • If the natural key is mapped and contains a value which does not exist in the application it will be created within the application.
For import types which only support insert (such as some transactions or print actions) a record will always be inserted.

Update Only

Only existing data will be updated. The following strategy is used to determine whether an update is performed:

  • If the natural key of the import type is either not mapped or empty an update will not be performed.
  • If the natural key of the import type is mapped and there exists a matching transaction or record within the application the record will be updated.
  • If the natural key is mapped and contains a value which does not exist in the application, no update will be performed.

Insert/Update

Where an existing record is found, it will be updated, otherwise a new record is created per the following strategy:

  • If the natural key of the import type is either not mapped or empty a new record is inserted.
  • If the natural key of the import type is mapped and there exists a matching transaction or record within the application the record will be updated.
  • If the natural key is mapped and contains a value which does not exist in the application it will be created within the application.

Delete Only

Delete operations are controlled explicitly by setting the "Delete Record" field to True, with the following strategy:

  • If the natural key of the import type is either not mapped or empty and the "Delete Record" field is set to True a delete will not be performed.
  • If the natural key of the import type is mapped and there exists a matching transaction within the application and the "Delete Record" field is set to True the record will be deleted from the application.
  • If the natural key is mapped and contains a value which does not exist in the application no delete will be performed.

Insert/Update/Delete

Combines the strategies of Insert, Update & Delete as described above.

Synchronise

Synchronise, where supported, provides the means to perform a differential comparison for each atomic transaction in the IMan dataset to the existing data within the application.

  • Add
    • New records are inserted into the application where there are records in the IMan dataset which do not exist in the application.
  • Edit
    • Existing records are updated in the application where there are matching records in the application when compared to IMan.
  • Delete
    • Where a record exists in the application, but does not exist within the IMan dataset, the record in the application will be deleted.

Consult the connector application's manual regarding specific details on how updates are handled.