When fetching saved report parameters (from the DB options table, parameters that were changed eg when changing sort order etc), we currently fetch the report parameters based on the controller action. If there are many reports available for the same report, they all apply the same viewDataTableParams.
This means a changed data table will never be applied for some reports. And if it was saved, it would be applied to all entities. This is why the report ID should be preferred over a plain controller action as it included eg also a goal id.
Need to see if tests still pass...