Is there a way to cap maximum rows e.g. 500 fetched from interaction history table when import interaction shape used in strategy
We are using NBAA V7.12. In current configuration for Import interaction, there are available filters based on last X days or using property based filters. Not seeing any capping based on max row returned like we have in report rules. Is there any other configs like any DSS or anything to cap on max rows returned from interaction history?
PEG
PL
Just a idea, if pega is using a report definition internally using a RD to fetch, then we can modify that RD to return the number of max result needed. You could trace and see if we can employ this to make this customization.
However, this could be a nice feedback and could be included in future product. I would suggest to raise a feedback item for the same.
Capgemini
IN
Thanks for your suggestion but I prefer to stay with current design using IH import shape instead switching to RD. Using RD is more complex implementation as need to take care joining with dimension tables too. I am more keen to know whether Pega internally use any configurable value to limit rows returned when generating and executing query on back of this IH Import shape configuration.
Pegasystems Inc.
NL
As mentioned in the earlier reply, only report definitions will give you the possibility of setting a limit on the basis of number of rows. The interaction history database table is not supposed to grow indefinitely–see this troubleshooting article. Starting with Pega Platform 7.4, we encourage looking at the functionality delivered by interaction history summaries.
Pegasystems Inc.
IN
In the Interaction history shape there is no option to limit the number of rows but there are other filters that can be applied to reduce the number of rows retrieved.