REST API and getting issues

Hi,

I am trying to parse all CSI's that are of certain type and are currently open using the REST API. They are written by our website into Tess and I want to programmatically update content in Tessitura based on the contents instead of having staff spend time working through them.

I'm having trouble getting the list of constituents out of the REST API that have an open CSI though.

The CRM/Issues resource only seem to allow me to search by an existing CSI Id or by a constituent.

I can't find a way to suck out a list through the REST API to get the list of consituents that way. I might be missing something obvious.

I can do it with some custom SQL using Custom/Execute but was wondering if anyone had a different bright idea so I could avoid that.

 

Thanks,

Nich

Parents
  • Hi Jennifer,

    We do use that report for manually finding them and processing them, unfortunately the reports also aren't available programmatically so I can't access the data in code. (At least I can't figure out how to get the results of a report through the API.

    Thanks,

    Nich


    Nich Young | IT Manager

    Sydney Theatre Company

     

    P +61 (2) 9250 1771 | M 0419 129 294 | nyoung@sydneytheatre.com.au

    The Wharf, Pier 4 Hickson Road, Walsh Bay NSW 2000

    P.O. Box 777, Millers Point, NSW 2000

    www.sydneytheatre.com.au


    On 22 June 2016 at 00:00, Jennifer Skelly <bounce-jenniferskelly8648@tessituranetwork.com> wrote:

    Couldn't  you just use the Customer Service Issue Tracking report? There is a "create by" filter in there, and you could just choose your web user. That's all we ever do when trying to find web created CSI's.

    From: Nich Young <bounce-nichyoung1302@tessituranetwork.com>
    Sent: 6/20/2016 11:56:28 PM

    Hi,

    I am trying to parse all CSI's that are of certain type and are currently open using the REST API. They are written by our website into Tess and I want to programmatically update content in Tessitura based on the contents instead of having staff spend time working through them.

    I'm having trouble getting the list of constituents out of the REST API that have an open CSI though.

    The CRM/Issues resource only seem to allow me to search by an existing CSI Id or by a constituent.

    I can't find a way to suck out a list through the REST API to get the list of consituents that way. I might be missing something obvious.

    I can do it with some custom SQL using Custom/Execute but was wondering if anyone had a different bright idea so I could avoid that.

     

    Thanks,

    Nich




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Reply
  • Hi Jennifer,

    We do use that report for manually finding them and processing them, unfortunately the reports also aren't available programmatically so I can't access the data in code. (At least I can't figure out how to get the results of a report through the API.

    Thanks,

    Nich


    Nich Young | IT Manager

    Sydney Theatre Company

     

    P +61 (2) 9250 1771 | M 0419 129 294 | nyoung@sydneytheatre.com.au

    The Wharf, Pier 4 Hickson Road, Walsh Bay NSW 2000

    P.O. Box 777, Millers Point, NSW 2000

    www.sydneytheatre.com.au


    On 22 June 2016 at 00:00, Jennifer Skelly <bounce-jenniferskelly8648@tessituranetwork.com> wrote:

    Couldn't  you just use the Customer Service Issue Tracking report? There is a "create by" filter in there, and you could just choose your web user. That's all we ever do when trying to find web created CSI's.

    From: Nich Young <bounce-nichyoung1302@tessituranetwork.com>
    Sent: 6/20/2016 11:56:28 PM

    Hi,

    I am trying to parse all CSI's that are of certain type and are currently open using the REST API. They are written by our website into Tess and I want to programmatically update content in Tessitura based on the contents instead of having staff spend time working through them.

    I'm having trouble getting the list of constituents out of the REST API that have an open CSI though.

    The CRM/Issues resource only seem to allow me to search by an existing CSI Id or by a constituent.

    I can't find a way to suck out a list through the REST API to get the list of consituents that way. I might be missing something obvious.

    I can do it with some custom SQL using Custom/Execute but was wondering if anyone had a different bright idea so I could avoid that.

     

    Thanks,

    Nich




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Children
  • Most reports call a stored procedure in the Database

    Think Customer Service Issue Tracking calls RP_CUST_SERVICE_ISSUE_TRACKING

    You could either expose this directly through the API (Custom/Execute with entry in TR_LOCAL_PROCEDURE ) or write a wrapper LP for it where you set the values for calling it  and would allow you to pre-process the data in the DB before returning it via the API.

    Mark