Question
SmartRules B.V.
NL
Last activity: 8 Feb 2021 4:40 EST
BIx Incremental load rule is working as Full load rule.
I have selected first check box on filter criteria tab i.e. "Use Last updated time as start". We are using pega bix 08.04 version. So ideally according to setting on filter crieteria I should get incremental records as output here. But this rule is running exactly same as that of Full load i.e. without chekcing filter criteria option.
I treid to resave the rule. Found few old articles where we can remove check box and ad condition by ourself like .pxCreateDateTime is Greater than "Last Extraction Time" ,But I this option is not working ,system shows error if we add "Last Extraction time" as literal string. In pega installing guide it mentioed that "Last extration time " will be replaced runtime. But I am not able to add that condition. Did anyone faced same issue and able to resolve.
I tried using pxCreateDateTime is greater than pxUpdatedatetime and its giving me less number of records, is this condition serve the same purpose as incremetnal load.
Updated: 26 Jan 2021 9:27 EST
LaunchSafe
US
Is the full load finishing? The first run of an incremental will do a full pull as there is no full to increment on top of. Further runs of this rule should be incremental. If this is not happening, make sure you are seeing a completed entry in pr_extract_time when the extract successfully runs.
SmartRules B.V.
NL
@Ryan_LAUNCHSAFE first of all thanks for checking and replying onto my query. I understand your point that you mentioned about running Incremental load first time will act as full load. but this is not the case here.
Finally I found the root cause here. Basically our other team has exposed few properties in the production environment and that caused to update pxSaveDateTime ,pxCommitDateTime and pxUpdateDateTime property for each and every row in the particular class. Hence it worked as full load.Even if you checked the option on the filter criteria "Use Last updated time as start". it acts as full load as the other internal properties updated because of property optimisation. You can refer below support article which explain how these properties gets updated in different scenarios.
https://community.pega.com/support/support-articles/bix-extract-rule-caused-full-load