Stop model re-query after table sort or filter

edited October 2019 in Questions
In a table created from Model A, I check boxes next to some rows, and press a button to now display only these checked records in the table.

To do this, I created another model (Model B), where after pressing the button the selected rows are adopted into Model B. Then, the all rows are deleted in Model A. And lastly, the rows from Model B are adopted into Model A. This works until I filter or sort.

I want users to be able to sort and filter on this selection. However, after sorting or filtering, Model A is re-queried and all records are displayed again.

Does anyone have a suggestion on how to stop the model from being re-queried after clicking filter or sort?

Thanks

Comments

  • edited October 2019
    An idea would be to create a condition on your primary model instead of adopting rows back in. You would make the condition "rows in another model". Set the model to your secondary model. Set it to filterable default off. Then in your action sequence, activate the condition.
  • edited March 2017
    Thanks! That worked perfect. Just had to add a model query I activate the condition.

    Really appreciate the quick response.
Sign In or Register to comment.