Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

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 list view rules

Updated on September 20, 2019


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
NameNot restrictive JOIN condition
MessageOne or more JOIN conditions potentially lead to cartesian product of tables and can adversely impact performance.

Suggested Approach

Check for the following when this warning occurs:

  • You did not choose the Equal to operator as part of the join condition when creating the list view.
  • You selected two properties for joining data that are completely unrelated in terms of 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.


Pega Platform 7.1.1 - 7.4 Reporting Financial Services Healthcare and Life Sciences Insurance Communications and Media Government Healthcare and Life Sciences Consumer Services Consumer Services Manufacturing Consumer Services

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us