Question
IBM
CN
Last activity: 27 Dec 2023 4:42 EST
Report definition fail to retrieve value for some properties from case
Hello,
In a report from a Report definition running, in which each line represent a case, found some properties from some cases are empty while some others are normal (non-empty)
As check in clipboard (pyWorkPage), in those problem cases, found the properties have normal (non-empty), wonder why they can not be shown in report.
may I know whether any possible reason?
the tricky part is that, some cases are normal.
Thanks.
Accepted Solution
Updated: 13 Aug 2023 14:12 EDT
Bits in Glass
IN
@MaxonL16591286 when you optimize properties, it will create a new column in the table and these newly created column will not have any value for existing cases. You would need to execute recreateindex activity for that.
So when you have created report and have those Columns in RD, values will be pulled from database Columns and as they were empty you were not able to see values.
Updated: 10 Aug 2023 5:25 EDT
NCS Pte. Ltd
SG
Hi @MaxonL16591286: Can you help to check in database table columns (in DB) for the cases where the values are empty. If the exposed columns has empty value, you will get this issue. But work page of the case still will get the values from BLOB.
Thanks.
IBM
CN
you are right, it's caused by the properties in DB are empty. We re-do the optimization on the properties then problem solved.
So it's a bit strange why they got empty in DB. Any possible reason?
Accepted Solution
Updated: 13 Aug 2023 14:12 EDT
Bits in Glass
IN
@MaxonL16591286 when you optimize properties, it will create a new column in the table and these newly created column will not have any value for existing cases. You would need to execute recreateindex activity for that.
So when you have created report and have those Columns in RD, values will be pulled from database Columns and as they were empty you were not able to see values.
Pegasystems Inc.
IN
@MaxonL16591286 You can check in the DB for the cases which don't have the particular value. This could be due to a property being exposed recently, which wouldn't have the value present for existing cases but will have the value for cases created post optimization. The workpage will have the values from the BLOB