Question
Maantic Inc
US
Last activity: 8 Nov 2019 16:30 EST
PYMESSAGEKEY column in History table returns different result when call from report definition and List view
Hi,
History table have property PYMESSAGEKEY.
Same property is referred in report definition and list view.
here report definition reads value from exposed column, List view reads value from blob.
List view is from OOTB - HistoryListView
How to force report definition to read value from blob column.
Note: Same property having different values in blob and exposed column
Pegasystems Inc.
CA
I guess the property having different values in blob and exposed column is the real issue. You need to fix that first. RD is correctly reading the value from the exposed column.
Pegasystems Inc.
US
HistoryListView is deprecated. It uses a custom getContent activity, getHistoryList. I assume something in this activity is forcing retrieval from the blob.
I agree with Praneeth, you need to sync the values in the exposed column with the values in the blob, rather than forcing the RD to read from the blob. The only way I can think of to do the latter would be to have the RD call a function alias that specifically calls pr_read_from_stream, and this would negatively impact the performance of the RD.
Pegasystems Inc.
IN
Hi,
How do you know that same property has different values in blob & exposed column.You need to fetch it using pr_read_from_stream() to read data from blob field.
Thanks,
Abhinav
Pegasystems Inc.
US
He can infer by looking at the generated SQL queries (e.g., in tracer with DB Query events enabled) for the list view vs the report definition. If the query for the LV has pr_read_from_stream calls it is reading those values from the blob. If the RD does not have pr_read_from_stream calls for the same property, it is reading from an exposed column. If the 2 reports have different values for the same property, then the values are out of sync.