-Using 6.10.12-
I have found a couple different issues with the Filter component.
-
On one of my screens, if the saved setting/value for “Show Rows” is greater than 50, the table is initially populated with 50 random records with no option to go to other pages of the table. When the “Search” button is clicked on the filter, the table is populated as expected. This issue disappears when the “Show Rows” is set to 50 or less. It only happens on the one screen so I’m not sure how to reproduce it.
-
I attempted to create a custom filter for invoice entities that looks into a composition relation to search within those child records. The invoice has many invoiceDetails. An invoiceDetail relates to one orderDetail. And an orderDetail relates to one product.
The weirdness that is happening is that this filter was not returning the expected results. I realized that the number of rows would consistently show one less than “Show Rows” value. And I think the fact that the rows count of the table never equaled the “Show Rows” value, it never showed the option to move to different pages. Increasing the “Show Rows” to a value larger than the expected count of results, still did not return all expected values. I found this by comparing the result from the JMX Console to the results from the filter. -
I have a filter on a TreeTable. The filter does not automatically enable the “Show Rows” component of the filter. If I set useMaxResult to true in init in the controller, the filter works as normal. The descriptor of the filter is set to useMaxResults.