Question
Hawaii Medical Service Association
US
Last activity: 23 Mar 2016 10:56 EDT
pxCommitDateTime value null for cases extract in BIX, what are the causes?
while extracting case data, i noticed the pxCommitDateTime value is null, what could be the reason and fix?
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems
IN
Which version of Pega 7 is this?
What is the value in the actual source table for this column?
sounds like an oversight. pxCommitDateTime property should not exist in the blob - it is in column only. Does bix have logic to take the pxCommitDateTime from outside the blob?
Hawaii Medical Service Association
US
Hi Andrew, Rajiv,
I queried fro the source report definition and no pxCommitDateTIme column is blank for any cases. what is the resolution?
sounds like a bug. I think current releases of BIX use the pzpvstream blob as source for all properties, while pxCommitDateTime lives in column only.
Hawaii Medical Service Association
US
is there any hotfix or work around?
I just quickly tested this and see the same. After including pxCommitDateTime in an extract, the output shows "", but if I open the WO and look at the clipboard, it has a value.
I don't see any existing instances of this being reported.
Gyan, please open an SR for this to be looked into and update this post with the SR number.
Pegasystems
IN
Was an SR created for this? If yes, please share the number.
Hawaii Medical Service Association
US
Hi,
SR has not been created on my end yet.
Hi Gyan,
Can you please let us know what version of BIX / Pega you're using?
Hawaii Medical Service Association
US
Hi Nicholas,
Pega 71.9 and BIX 7.10
Pegasystems
IN
I am assuming you are using the BIX version found in the additional products folder of the Pega 7.1.9 distribution image (and not an older / newer one). The highest ruleset version for Pega-BIX in Pega 7.1.9 should be 07-10-19.
Hawaii Medical Service Association
US
yes,i saw we have the highest rsv Pega-BIX:07-10-19
Pegasystems Inc.
US
On a related note, what will BIX use to determine incremental updates if a table does NOT have the pxCommitDateTime column added?
Hawaii Medical Service Association
US
I believe we can use Use last updated time as start which is a has a property pyUseLastUpdated.
Pegasystems
IN
Please refer to the BIX user guide - https://docs-previous.pega.com/bix-71-user-guide
Please refer to the BIX user guide - https://docs-previous.pega.com/bix-71-user-guide
Use Last Updated Time as Start For classes that include the property pxCommitDateTime, select this check box to extract all data that was created or updated since the last time the Extract rule was run. This field is not relevant until the Extract rule has run at least once. Note: If you select the incremental extraction option, a filter condition is automatically included during an extract that restricts extraction to class instances where the pxCommitDateTime property value is greater than or equal to the last date and time when the extract ran. pxCommitDateTime is automatically set for each class instance when it is changed in the database by the Pega 7 Platform database regardless of how the data was created or changed (interactively by an end user, programmatically by an activity, through an import, or by any other means). This condition is added to any others you specify on this tab. Sometimes the pxCommitDateTime property may need to be added as a database column to the class table. For example, it is not added automatically on upgrades. An extract using the incremental extraction property will fail if this column does not exist in the class table. Also note that when incremental extraction is performed, class instances with NULL values of the pxCommitDateTime property will be skipped and when using the -c command line option to extract from child classes, those child classes whose class tables do not include the pxCommitDateTime property will be skipped. Do not select this check box if you plan to run the Extract rule using the command-line and intend to use the -d, -D, -u, and -U parameters. This is because these parameters do not override the check box setting , which can result in unanticipated results from a command-line extract.
Hawaii Medical Service Association
US
Hi Rajiv,
PRPC table gets populated for the pxCommitDateTime, however, the values are not extracted (all values null for pxCommitDateTime) in the target database. I am planning to use agent to schedule the extraction, do I need to be concerned?
Hi Gyan,
If you're not concerned with the value of pxCommitDateTime in the target database, then you probably don't need to worry about it. If this is a piece of data that you are required to track, then please raise an SR for us to look into it. As I said, I was able to reproduce.
Hawaii Medical Service Association
US
Hi Nicholas,
What would be the need of pxcommitdate time over pxUpdateDateTime?
Updated: 22 Mar 2016 15:30 EDT
Hi Gyan,
From the latest help: https://community.pega.com/sites/default/files/help_v72/procomhelpmain.htm
pxCommitDateTime - Records the time when a record or updated rule was committed to the database. *Generally more accurate than pxUpdateDateTime
pxUpdateDateTime - Date and time of the most recent update to the work item.
In terms of the 'need' for these in a target database, this is something that you need to determine based on your business requirements.
If you find that you require pxCommitDateTime to be populated with an accurate value in the target database, then please raise an SR for this to be looked at.
Pegasystems
IN
Note that you can do a Property-Set of the pxUpdateDateTime value in an activity / data transform and that value could be in the past or future and when the instance is saved, the value set is persisted. The same is not the case with pxCommitDateTime. pxCommitDateTime is set by the platform at the time of commit to the database.
Hawaii Medical Service Association
US
Hi Rajiv,
Thanks for the information. is the issue of pxCommitDateTime not sent to the target database is known issue? do you know isthere a hot fix ready ?
Pegasystems
IN
I don't believe there is any hotfix available. Please raise a SR as suggested by Nicholas
Pegasystems Inc.
US