How to correct the Not Restrictive JOIN Condition warning for list view rules
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 Type | Warning Type | |
|---|---|---|
| Rule-Obj-ListView | Performance | |
| Name | Not restrictive JOIN condition | |
| Message | One or more JOIN conditions potentially lead to cartesian product of tables and can adversely impact performance. | |
| Details | N/A | |
| Severity | 2 | |
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.