pr_read_from_stream is used for the optimised property
in one of our environments (in fact, in a PROD), reports in Pega 7.1.8 run sql with pr_read_from_stream on a simple property from PC_*_WORK table that is optimized (moreover, index on this property is created in the table). Table PC_*_WORK contains 350000+ of records, property is used in a when condition, so this is realy an issue.
Property was optimized via Pega in all environments. Actually, in all of them it is absent in the External mapping of the class rule, but in DEV and UAT sql uses corresponded field, while in PROD it uses blob for this property.
that is in PROD-environment where we don't have access to Pega-application. Still DBA run for us the simplest query to check if column in the table has values for new cases - column has values, everything looks correct in db
Posted: 3 years ago
Posted: 28 Jul 2017 9:49 EDT
Celeste Dufresne (CelesteDufresne_GCS)
Principal Software Solutions Engineer
Actually I just reread this and you are saying reports are not using the exposed column so it seems like the class mapping is wrong. Did you optimize it by right clicking on the property and saying to optimize for reporting through the UI?
It seems strange that if the class mapping is updated and when you run Property-Seek-Value it is able to populate the exposed column but the report doesn't seem to know about it. Are you seeing this issue with multiple reports or is there just one that uses the property? You might try resaving that report definition and see if that helps. Otherwise I would suggest an SR.
Resaving the report or resaving the class rule will be the one of the last actions since organizationally manipulations in PROD in this project are strongly limited. Still we can try to create something like a patch-version with the same version of the rule of the report.
To check other reports is a good idea also, thanks.