• Replies 19 replies
  • Subscribers 0 subscribers
  • Views 60 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

  • I'd like to provide some comment to this thread, given our years of using Collaborate, and the customisations we've implemented to provide advanced features beyond Collaborate's OOTB capabilities.

    Firstly, if we are talking about using the ExportXML feed from within Collaborate (Home/Wiki), then improving the XML feeds is a waste of time, given it's fundamental limitations on some column types. We went down this road back in the V3 days, whilst also going down the RenderXML route to facilitate the searching capabilities (that you are seeking).

    Once V4 came along and the iSheet API's matured, we switched to using these instead, from within Collaborate, which we use together with our GraphQL wrapper around their API's (where we can extend/improve upon).

    The better approach would be that HighQ create an API within Collaborate to allow "page developers" to easily and securely obtain an API token for the current user, and to then be able to call the Collaborate iSheet (Search) API's. The results will have none of the limitations of ExportXML, and as a bonus you now have access to all the API functionality this user can perform, i.e. folder generation, silent iSheet item status changes, etc etc.

    Andrew

Reply

  • I'd like to provide some comment to this thread, given our years of using Collaborate, and the customisations we've implemented to provide advanced features beyond Collaborate's OOTB capabilities.

    Firstly, if we are talking about using the ExportXML feed from within Collaborate (Home/Wiki), then improving the XML feeds is a waste of time, given it's fundamental limitations on some column types. We went down this road back in the V3 days, whilst also going down the RenderXML route to facilitate the searching capabilities (that you are seeking).

    Once V4 came along and the iSheet API's matured, we switched to using these instead, from within Collaborate, which we use together with our GraphQL wrapper around their API's (where we can extend/improve upon).

    The better approach would be that HighQ create an API within Collaborate to allow "page developers" to easily and securely obtain an API token for the current user, and to then be able to call the Collaborate iSheet (Search) API's. The results will have none of the limitations of ExportXML, and as a bonus you now have access to all the API functionality this user can perform, i.e. folder generation, silent iSheet item status changes, etc etc.

    Andrew

Children
No Data