I have replaced the default runs.html and results.html pages in an assay with custom pages. These custom pages load a QWP with the corresponding assay domain query. On the run page, each run name has a URL that points to the result page, filtered on that runId:

../assayResults.view?rowId=43&MHC_SSP_Data.Run/RowId~eq=40

If I follow this url, it loads the custom results.html page. This page loads a QWP of the results domain. The problem is that when loading a QWP, it does not by default look in the URL for filters. What's the most robust way to handle this?

One option is to put code on my page that looks for filters/sorts in the URL and adds them to the QWP when loading. It'll work, but I dont think filters added in this way are removable (there's a bug on 'clear all'). In this specific instance, I know what URL params to expect and I know what QWP they will apply to. However, if this same idea comes up in another context, this won't work so well. What if I have two QWPs embedded in a page? Is there a more robust solution? Is there any code in the API or QWP that I can take advantage of? is there any javascript code to parse filters out of the URL? does the QWP have any features I dont know about that might assist here? thanks for the help.