Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

How to correct the Not restrictive JOIN condition warning for summary view rules

Suggest edit Updated on September 20, 2019

Summary

Remediate this high-priority warning before using the rule in a production environment.

In v5.4 sp2 or greater, use the Download High Priority Warnings option in the Application Preflight tool to research all high-priority warnings in your application. As a best practice, perform the preflight check before you lock a RuleSet version.

Rule TypeWarning Type
Rule-Obj-SummaryViewPerformance
NameNot restrictive JOIN condition
MessageOne or more JOIN conditions potentially lead to cartesian product of tables and can adversely impact performance.
DetailsN/A
Severity2


Suggested Approach

This warning usually occurs if you selected two properties for joining data that are completely unrelated in terms of field values. Every row in the first table (of n rows) will be joined with the second table (of m rows) resulting in a result set of a total of m X n rows.

Use PAL to monitor performance when you create a new report using joins. 

Tags

Pega Platform 7.1.1 - 7.4 Reporting Financial Services Healthcare Insurance Media and Advertising Government Life Sciences Utilities Hospitality and Entertainment Manufacturing Retail
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us