• Replies 5 replies
  • Subscribers 0 subscribers
  • Views 20 views
  • Users 0 members are here
Options
3sides - Social sharing widget
Related

Pre-filtering XML Feed

Mark Salamon
27300

Does anyone know if it's possible to pre-filter the response returned by the XML feed (i.e., filtering on the server side), rather than returning ALL of the records in the selected view and being forced to filter on the client side?

I have tried the following technique but gotten very mixed results, attaching to the end of the XML URL ("&metaData.isheetExportType=xml") the same parameters that are added when running an advanced search from the site.  For ex:

...&advanceSearch=true&filterValue_{COL_NUM}_1={URL_ENCODED_VALUE}

I have tried this both in the browser's url field and when making an ajax call on the client side.  Often, the first time I make this call it works, but then the next time it returns the same results as the first call, even if I am using a different filter value.  Sometimes the initial call does not filter at all or filters on the wrong value.  It appears that something is cached, but given that the url parameters are changing, I don't know why that would be.  And when trying from the browser's url field, I get different results in Chrome and Edge?

Is this technique possible but more is required to make it work or is there an alternative?

  • Ryan McDonough I can't "like" the answer, because I would have preferred a different answer :) but I appreciate your responding. Btw, THIS technique does work to return a single item, adding this: &metaData.itemId={ITEMID}

  • Mark Salamon that's really useful to know actually, you could maybe make a slim view which has stuff you want to search against, do that in JS when it comes back, then you could then get the individual items by their ID?

  • Ryan McDonough This is one reason I asked the question above, because I was playing around with adding the parameters that work inside the page onto the XML feed. the advanced search parameters worked inconsistently and this direct access to an item worked. (I'm assuming under the hood there is overlapping logic.) There may be other url parameters that would work... if there are any others.

  • Hi Mark Salamon. Similiar to my one here and some interesting points were discussed : https://collaborate.highq.com/sitepoint/blogHome.action?metaData.siteID=714&metaData.blogCategoryID=0&metaData.blogID=7306

    The comment about the item id though, I will be checking that out thanks!