If a query section exists in a record, that query section has a “Find” and “Remove”. If that query has a “Group By” in it, the “Remove” will issue a MID error (even though the removal actually takes place) if filter criteria are applied before clicking “Remove”.
The problem does not occur if no filter criteria are applied before clicking “Remove”, or if the query associated with the query section does not have a “Group By”. This problem was seen in multiple releases including TRIRIGA 220.127.116.11 and 18.104.22.168.
We needed to change the submit of the page method to “Get” for non-state-changing actions like “Refresh” or “Clear Filter”. The “De-Associate” action on the “Group By” report no longer throws any exception after applying a filter to the query.