Question
Cognizant
IN
Last activity: 29 Aug 2022 11:24 EDT
Filter criteria for BIX Extract: based on "Last Extraction Time"
How to fetch the pega query running in the back end, when in the extract rule we have given a filter condition.
.pxupdateDateTime >= Last Extraction Time
How to get the "Last Extraction Time" value, so that it's getting compared every time to the previous value.
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Allianz Technology
DE
@PavithraN0216 Hi, could you please explain a bit more why would you need to compare Last Extraction Time with the previous value? When you specify ".pxupdateDateTime >= Last Extraction Time" in the extract rule you are already taking the records updated post to the last extraction time, so I need more details to understand your use case and potentially help.
Updated: 2 Jun 2022 7:45 EDT
Cognizant
IN
@Oleg Shepelev If I am to create a test document, to compare the Last Extraction time. To verify that it's taking the previous extract time, every time the extract is run. I would like to know how does this "Last extraction time" gets it value from the database, what is the query running behind. Hence I can compare it with the query runner's pylastupdatedate.
Cognizant
IN
Thanks for the reply@Oleg Shepelevwanted to understand how does this "Last Extraction Time" being used. What is the query running behind. Hence I can compare it with the EXTRACT_TIME's PYLASTUPDATEDATE value. As we need to monitor the changes in the extraction time value, the next time the extract being run.
Allianz Technology
DE
@PavithraN0216Hi! Not sure about the exact logic laying behind "Last Extraction Time" but as there is a Execution History tab in the Extract rule where the datetime of the last execution is captured I believe that's the source of it. According to the logic of the source for this grid the execution time is taken from the property .pxCreateDateTime of Log-Extract class filtered by .pxCreateOpName, so you may get it from there. (See the sreenshots).
Hope it helps!
Cognizant
IN
@Oleg Shepelev Thanks for the reply, if as you say "Last extraction Time" takes the value of createdatetime from extraction history tab, then the value of this has to be equal to "pyLastUpdateDate" of EXTRACT_TIME table as well right? But it's not being equal . If you could guide me here.
Allianz Technology
DE
@PavithraN0216Could you please share the screenshot of the discrepancy that you see there? Could it be just the time zone difference?
Cognizant
IN
@Oleg Shepelev Yes, sure have shared both the screenshots. The 2nd screenshot is after running
the query "SELECT * FROM PegaDATA.PR_EXTRACT_TIME ORDER BY PYLASTUPDATEDATE DESC;" from query runner. In that case there is a gap of around 1 hour I suppose. But it has to be equal right. Kindly look into it.
Pegasystems Inc.
US
@PavithraN0216 @Oleg.Shepelev
I have a similar question.
What does the value pyLastUpdateTime in the table PegaData.pr_extract_time represent?
Is it the LastExtractionTime that will be used as filter criteria for the next extract? OR
the LastExtractionTime value that was used for the most recent run extract?