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

XML feeds with search parameters?

David Corrin
27314

Hi all,

XML feeds are very useful, however it is not very efficient to download the entire iSheet to find the one(or more) records that I want to display on screen.

Has anyone found a workaround to leverage search parameters in the xmls feeds,? (similar to how advanced searches work)

Thanks,

Parents

  • Referencing my duplicate post on this topic (apologies) -- https://collaborate.highq.com/sitepoint/viewBlog.action?metaData.siteID=714&metaData.blogID=7432. I agree that overall it would be better to find a way to leverage making REST API calls from within the page, rather than enhancing the XML feed. That said, having been in software development for a long time, that's going to be a big lift. I suspect that enhancing the XML feed in a two small ways would be fairly easy to implement and sooner, and would have a large impact on many existing projects, echoing what David Corrin said.

    1 - Support the same parameters used in Advanced Search (and used for drill down purposes from the charts). My limited testing shows that this seems to work in a very limited and inconsistent fashion. My suspicion is that under the hood there is some common code that would make this possible. Note that this url parameter that can be used with the web URL DOES work to limit what is returned to a single item: &metaData.itemId={ITEMID} . (Another reason I believe the XML and web URL have common code paths.)

    2 - Fill in the content gaps in the XML feed. For example, include the fileid for files used in file links (and folder ids for folder links). I have not put together a comprehensive inventory of all of the gaps. I find for most column types the information returned by the XML is sufficient if not complete. The gaps seem fairly small. Andrew Quinn you may know of others? This information is obviously available and I can't imagine adding it to the XML feed could be difficult.

    More complex would be supporting a feature like pagination. If we had the ability to filter, that would help in a big way and pagination would not be as important in many situations. I would prioritize the two features above, which are likely the easiest, then consider whether other enhancements make sense.

Reply

  • Referencing my duplicate post on this topic (apologies) -- https://collaborate.highq.com/sitepoint/viewBlog.action?metaData.siteID=714&metaData.blogID=7432. I agree that overall it would be better to find a way to leverage making REST API calls from within the page, rather than enhancing the XML feed. That said, having been in software development for a long time, that's going to be a big lift. I suspect that enhancing the XML feed in a two small ways would be fairly easy to implement and sooner, and would have a large impact on many existing projects, echoing what David Corrin said.

    1 - Support the same parameters used in Advanced Search (and used for drill down purposes from the charts). My limited testing shows that this seems to work in a very limited and inconsistent fashion. My suspicion is that under the hood there is some common code that would make this possible. Note that this url parameter that can be used with the web URL DOES work to limit what is returned to a single item: &metaData.itemId={ITEMID} . (Another reason I believe the XML and web URL have common code paths.)

    2 - Fill in the content gaps in the XML feed. For example, include the fileid for files used in file links (and folder ids for folder links). I have not put together a comprehensive inventory of all of the gaps. I find for most column types the information returned by the XML is sufficient if not complete. The gaps seem fairly small. Andrew Quinn you may know of others? This information is obviously available and I can't imagine adding it to the XML feed could be difficult.

    More complex would be supporting a feature like pagination. If we had the ability to filter, that would help in a big way and pagination would not be as important in many situations. I would prioritize the two features above, which are likely the easiest, then consider whether other enhancements make sense.

Children
No Data