Integrations and APIs for Service

Get Involved. Join the Conversation.

Topic

    Prasad
    Error when using RNService.RunAnalyticsReportAnswered
    Topic posted October 16, 2018 by PrasadRed Ribbon: 250+ Points, last edited October 17, 2018, tagged SOAP 
    74 Views, 5 Comments
    Title:
    Error when using RNService.RunAnalyticsReport
    Summary:
    Error when using RNService.RunAnalyticsReport
    Content:

    Hi,

    i am not able to use RunAnalyticsReport with RNT service. getting attahced error message. please help me how to fix it.

    .Net Framework: 4.6

    VS: 2107 professional

     

    Thanks

    Prasad

    Best Comment

    Prasad

    i found the solution from below article.

    https://cx.rightnow.com/app/answers/detail/a_id/9838/kw/rightnow%20wsdl%20url%20not%20working

     

    Comment

     

    • Prasad
    • Robert Surujbhan

      HI Prasad - try something like this. Using the CCOM 1.4 service definition, you need to specify the CSVTableSet as an 'out' parameter to the RunAnalyticsReport operation.

      APIAccessResponseHeaderType resp = _RNService.RunAnalyticsReport(cih, aPIAccessRequestHeader, analyticsReport, limit, start, ",", false, true, out reportTable, out output);
      
    • Prasad

      Hi Robert,

      thanks for your quick reply. i have tried this approach but same not working for me.

      i am using API url in below format. 

      https://<sitename>/services/soap/connect/<service>
      

      standard format not working for me. 

      https://<host_name>/cgi-bin/<interface>.cfg/services/soap?wsdl
      

      Thanks

      Prasad

    • Prasad

      i found the solution from below article.

      https://cx.rightnow.com/app/answers/detail/a_id/9838/kw/rightnow%20wsdl%20url%20not%20working

       

    • Robert Surujbhan

      Hi Prasad - the code you posted earlier indicated that you might be using the 1.4 version of the service (/services/soap/connect/soap?wsdl) and that's where you need to call RunAnalyticsReport in the way I mentioned.  Perhaps your environment was upgraded and that's where 1.4 became the default.  If you want to use the older 1.3 version, that's where the input parameters differ. Just wanted to clarify this! 

      For obvious reasons, you should consider using the newer and current 1.4 version of the SOAP service.