Hi,
Is there any alternative way for creating reports of non-optimized property
@AbhishekC1725 please refer the below URL for reference. But best practice is to use optimized properties in report definition.
https://support.pega.com/question/how-add-unoptimized-property-report-definition-query-tab
@AbhishekC1725 You can make use of elastic search but there are few limitations.
@BhanuPrakash_G Thanks will try this
@Anoop Krishna Thanks will check this also, actually need to optimized page-list property according to requirement.
@AbhishekC1725 Then you need to use index table. Pagelist data will be stored in index table and from the main report you need to join index table to get that indexed pagelist data. Please refer below URL for reference.
https://onestoppega.com/decisioning-declarative/declare-index-in-pega/
@BhanuPrakash_G @AbhishekC1725
Elastic search won’t work if you need to do joins.
The best practice is to optimize the columns required for reporting. Please remember - reading from the BLOB is a costly operation and there could be performance issues.
@Anoop Krishna Thanks Anoop, We manually created index class for declare index, because current application have some different levels where properties are defined. But thanks for support.
@AbhishekC1725 sure welcome, ya as I mentioned for optimizing pagelists index tables are required which inturn needs a class. Please accept the above comment as you solved your problem with that approach.