| Description |
In the case of http://jira.irelyserver.com/browse/FRD-897 we had an issue where the sort would not finish correctly and it would cause invalid row calculations pointing to a row name or some row type that cannot be used.
We have the JIRA to correct the re-sort issue, but I would like to institute a check upon saving the row design to make sure there are no infinite loops.
While the issue that it will not generate if a row calc is pointing to a row name is frustrating, it only effects the reports. The issue where we have infinite loops, if not handled quickly, can slow the server down to where working in any module is near impossible.
This would help reduce major server wide problems that could be created by reports.
Steps to Reproduce:
1. In SQL adjust a row calc to use itself (With the sorting being fixed this will be hard or impossible to reproduce at this time)
2. Run the report while watching the FRD App pools resources, they will creep up to a point where the server is at 99%-100% CPU usage.
Acceptance Criteria:
-Upon Saving, and after the sort, check row calculations for rows that use themselves in the calculation
-Throw error message that lets the user know that a row calculation is incorrect
-If there are any rows that violate this, call the highlight rows > Invalid Row Calc procedure to highlight the offending rows
|