Posted: 19 Aug 2015 7:40 EDT Last activity: 21 Aug 2015 4:45 EDT
We have the BIX framework installed on top of our application.
As per the BIX documentation it is not possible to only extract delta's from the classes like Assign- and History-. This is because the pxUpdateDate column does not exist for these tables and BIX uses this to identify the delta records.
However we have made this working by manually adding a column to the history table called pxUpdateDateTime. The value inserted here is autogenerated by the Oracle DB (Default value) and inserts the current system time whenever a new record is added.
The question actually is....while this seems as an easy enough solution should we actually be doing this and are we not affecting the BIX functionality in some kind of negative way?
For history classes BIX does use the pxTimeCreated column instead of pxUpdateDateTime
Also in the BIX command line you can use the -d and -D options to give the date range for pxCreateDateTime
That said, with 7.1.8 we are using the pxCommitDateTime column. This is system generate time on when the record is committed to DB rather pxUpdateDateTime which can be set by the user to any value.
Also, in the forthcoming 7.1.9 release you should be able to use any datetime property in the Extract rule filter conditions in the ruleform to define you own incremental extraction against a symbolic date to represent the Last Extraction Time.
Which version of Pega platform and BIX are you using?
I'm a bit confused here. So you're saying that if I check the Delta option in BIX (for a history class) it should identify the delta records based on pxTimecreated rather then pxUpdateDateTime. This does not seem to work and in addition in contradicts what is stated in Bix documentation.