Database integrations are not supported for XML and SAP IDoc database providers.
New Record Detection Property Page |
Use the New Record Detection property page to configure how the Integration Service detects database updates for your integration.
|
|
Database integrations are not supported for XML and SAP IDoc database providers. |
Database Connection
Database Connection Setup: Starts the Database Setup wizard, where you can connect to the database that you want the Integration Service to monitor. For more information about how to use the Database Setup wizard, refer to Database Setup Dialog.
Database Type: Displays the database type after you complete the database connection setup.
Location: Displays the location of the database after you complete the database connection setup.
Poll Interval: Specifies how often the Integration Service checks the database for changes.
New Record Detection Method
Use the new record detection options to specify the database trigger event that the Integration Service detects and which database records it processes.
|
|
For text-based database types, such as text file, Microsoft Excel, and Microsoft Access, Integration Builder supports only the Field has increasing value and Field has newer timestamp new record detection methods. |
Use all records, and remove when done: Specifies that the Integration Service processes all the records in the specified database and then deletes them. Available for database connections that are writable by BarTender and where the monitored table has a primary key.
Copy to other table: Specifies that the processed records are copied to another table before they are deleted from the original table.
Table: Specifies the table that you want to copy the processed database records to.
Field has increasing value: Specifies that the Integration Service monitors the specified field for an increased value.
Field: Specifies the field that is to be monitored. This field must be a numeric field that increases in value, such as an automatically incrementing ID number.
Last value: Specifies the value that the Integration Service monitors for. This field can be populated manually or automatically, as follows:
To populate the field manually, enter the value that triggers the integration. For example, if the database contains rows that have the values 1 through 5, you can enter 3 in the Last value field to cause the integration to be triggered from 3 onward.
To populate the field automatically, click Reset to Last Field Value. The Integration Service searches for the highest value in the specified database field and then populates the Last value field with that value plus 1. The service then monitors for the incremented value.
Reset to Last Field Value: Causes the Integration Service to search for the highest value in the specified database field and then populate the Last value field with that value plus 1. This incremented value also appears in the Next expected value field.
Next expected value: Specifies the value that the Integration Service uses to trigger the integration. This value is updated automatically in the following ways:
By triggering the integration
By manually adding a value to the Last value field and then clicking in any other field on the page
By clicking Reset to Last Field Value
Field has newer timestamp: Specifies that the Integration Service monitors the specified field for a newer timestamp.
Field: Specifies the field that is to be monitored. This field must uniquely identify the record and must increase in value each time a record is created or updated.
Last value: Specifies the timestamp that the Integration Service monitors for. This field can be populated manually or automatically, as follows:
To populate the field manually, enter the value that will trigger the integration.
To populate the field automatically, click Reset to Last Field Value. The Integration Service searches for the highest value in the specified database field and then populates the Last value field with that value plus 1 of the smallest time unit. The service then monitors for the incremented value.
Reset to Last Field Value: Causes the Integration Service to search for the newest timestamp value in the specified database field and then populate the Last value field to that value plus 1 of the smallest unit. This incremented value also appears in the Next expected timestamp field.
Next expected timestamp: Specifies the timestamp value that the Integration Service uses to trigger the integration. This value is updated automatically in the following ways:
By triggering the integration
By manually adding a value to the Last value field and then clicking in any other field on the page
By clicking Reset to Last Field Value
Field has specified value: Specifies that the Integration Service monitors the specified field for a specific value. It then processes each record where the value is found in that field. This option is available for database connections that can be updated and where the monitored table has a primary key. Available for database connections that are writable by BarTender and where the monitored table has a primary key.
Field: Specifies the field that is to be monitored.
Value: Specifies the value that the Integration Service is monitoring for in the specified field.
Update field after processing: Specifies that the Integration Service is directed to update the monitored field, replacing the value that was detected with a new value. When the value in the monitored field is updated, the record will not be re-processed when the database is next polled by the Integration Service. This option is available when the monitored table has a primary key. A primary key is essential to find the exact record to update.
New Value: Specifies the value with which to update the monitored field after the record has been processed.
Actions After Failure
Use these options to specify the actions that you want to be performed for the database record if one or more of the integration actions fail.
Retry all actions for this database record: Specifies that all the actions for the database record are retried.
Skip this database record: Specifies that the database record is skipped.
Copy to other table: Specifies that the skipped record is copied to another database table for later processing or for logging purposes. Use the list to select the table that you want the record to be copied to. This table must have the same table schema as the source table.
Related Topics