| Info | ||
|---|---|---|
| ||
| Make sure that Delta mode is supported by the extract you are going to use, see the Cross-Reference of Objects and Filters table. |
In this page:
| Table of Contents |
|---|
DeltaBased Parameter
Default value is "N".
...
- You decide on an specific string UID you are going to use, say, mydelta1.
- Use it with the DeltaBasedUID parameter in the control message.
- Other users with other UIDs performing the same extract in Delta mode, will not interfere into your workflow (unless they specify your UID) and you will be getting added or modified records in a more predictable way.
The “last run time” value for delta extract is stored based Based on extract feed type AND DeltaBasedUID value, the process stores the “last run date” value and the last instance used for delta extract, so if you run two extracts with the following task parameters: FeedType=SMFEXTRACT, DeltaBased=Y, DeltaBasedUID=mydelta1 AND FeedType=SMFEXTRACT, DeltaBased=Y, DeltaBasedUID=mydelta2, then two separate “last run time” date” values will be stored: one for mydelta1 and the other for mydelta2.
...
| Code Block | ||
|---|---|---|
| ||
<taskParameter>
<name>DeltaBased</name>
<dataType>S</dataType>
<value>Y</value>
</taskParameter>
<taskParameter>
<name>increaselastrundatetime</name>
<dataType>S</dataType>
<value>ONLY_DATA_EXTRACTED</value>
</taskParameter> |
UseInstance Parameter
Toggles instance usage by resolving vDeltaDBInstance - primary key of the DB table - in extract_delta_based_param.inc
| Code Block | ||
|---|---|---|
| ||
<taskParameter> <name>UseInstance</name> <dataType>S</dataType> <value>Y</value> </taskParameter> |
...
If the extraction was successful, then the PACE_MASTERDBO.ORCH_REQUEST_PARAMS table will recieve receive new values for delta info and the following fields will be updated or added:
...