Page Comparison

Default value is "N".

If this parameter is set to Y then only the data added or updated since the last event of extraction with DeltaBased=Y will be extracted. This way you can extract new records that have been recently added or modified.

Example: Delta Based Filter without any additional options

       <taskParameter>
              <name>DeltaBased</name>
              <dataType>S</dataType>
              <value>Y</value>
       </taskParameter>

DeltaBasedUID

...

was added in June 2016 EagleML release

DeltaBasedUID Parameter

1. You decide on an specific string UID you are going to use, say, mydelta1.
2. Use it with the DeltaBasedUID parameter in the control message.
3. 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.

...

• If Generic Extract is launched with DeltaBased=Y and profile without setting the DeltaBasedUID value, profile name will be used as DeltaBasedUID value.
• You cannot use different DeltaBasedUIDs for different feedtypes within one control message for Generic Extract workflow. All extracts will use the same DeltaBasedUID.

Example: Delta Based Filter with Delta Based UID

       <taskParameter>
              <name>DeltaBased</name>
              <dataType>S</dataType>
              <value>Y</value>
       </taskParameter>
       <taskParameter>
              <name>DeltaBasedUID</name>
              <dataType>S</dataType>
              <value>mydelta1</value>
       </taskParameter>

You can change the way your delta extract handles the last run date value by specifying the increaselastrundatetime task parameter in your RTR for a specific extract (higher priority) or by setting its global version in w_config_custom.inc

DeltaBased increaselastrundatetime Option

...

• ALWAYS (default) - always rewrite the last run date value after delta-based extraction
• NEVER - switches off rewriting last run date
• ONLY_DATA_EXTRACTED - changes last run date only if some data has been extracted

Example: Delta Based Filter with increaselastrundatetime

       <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

       <taskParameter>
              <name>UseInstance</name>
              <dataType>S</dataType>
              <value>Y</value>
       </taskParameter>

...

• GWDELTA_ - common prefix for delta process
• :DeltaBaseUID: - unique identifier of the process
• :FeedType: - feedType value without the EXTRACT suffix

...

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:

...