I'm using the ExportXML method + Javascript to display/process some isheet data on a HighQ homepage, as I think a lot of people on here do . I've noticed is that the export URL/method ("./sheetViewExportXML.action?metaData.siteID=xxxx"&metaData.sheetId=xxxx&metaData.sheetViewID=xxxx &metaData.isheetExportType=xml")  seems to remember the last search made on the iSheet, exporting only the data that satisfies the last search (even if the window/tab with the search results is closed), resulting in incomplete data being pulled by the Javascript code. For example, let's say a homepage uses the above method + jquery to display every value of an iSheet column. The user views the homepage and sees all records from the iSheet in the content panel; if they then go to that iSheet, do a search, then go back to the homepage, they will then only see the values of records that satisfy that search on the homepage.

Other than manually going back into the iSheet to clear the search, is there any way to ensure that the complete iSheet data is grabbed with the ExportXML? Even searching in a different view than the one in the "viewID" parameter affects the data pulled by the ExportXML. 

The current (extremely clunky, kind of slow, and, at least in firefox, kind of buggy) workaround I'm playing with is putting the entire iSheet in a 0x0 iframe in the same panel as my javascript, waiting for that to load before attempting to grab the data. I've seen some people on here requesting the ability to use search parameters with the ExportXML URL, which would also be helpful, but is there anyway to "reset" or ignore the search state of the isheet when calling ExportXML, or is that baked into the function?

I'm wondering if anyone else has run into this, and if there's any solution, or a workaround more elegant than mine.

Thanks!