Custom Rest Connector to my App

Comments

8 comments

  • Avatar
    Oxana Noa Umansky

    Hi Jason,

    It's more suited to reach out to our support team directly to solve this issue. 

    I'll open a ticket for you and our team will be happy to assist. 

    Thanks,

    Oxana

    0
    Comment actions Permalink
  • Avatar
    Michael Becker

    Hi Jason,

    I do not think you can use syntax like that - "Path": "Mobile/[@Tables.Token.@.Ticket]/ExportAccount", you don't have Ticket parameter defined anywhere. What's more Sisense, I think, will not allow you to use array in path parameter. But as Oxana suggested it is better to run it by support.

    Regards,

    Michał

    1
    Comment actions Permalink
  • Avatar
    Jason France

    I am trying to follow the instructions in the online documentation for referencing a value returned from "table A" for use in in a "table B" call, similar to this documentation.  I'm sure I'm not capturing and referencing the Ticket value correctly... 

    https://developer.sisense.com/pages/viewpage.action?pageId=3702834

     

    0
    Comment actions Permalink
  • Avatar
    Jason France

    It's like the first table request for the Ticket isn't returning anything.  Maybe because the Body isn't formed correctly to match the MVC class on the server.  The server is looking for {"Username":"Me","Password":"pass"}.  But without using something like WireShark, I don't know if that is being passed correctly with the body tag

     

    2018-02-09 14:03:34,528 [198] [NT AUTHORITY\SYSTEM] DEBUG RestRequestHandler - ExecuteActionAsync: Tables.Token, stopped, retreived 0 document(s), totally retreived 0 document(s), hasMore = False
    2018-02-09 14:03:34,528 [120] [NT AUTHORITY\SYSTEM] DEBUG RestRequestHandler - ExecuteActionAsync: Tables.Token, stopped, retreived 0 document(s), totally retreived 0 document(s), hasMore = False

    0
    Comment actions Permalink
  • Avatar
    Conor Hennessy

    Hi,

    Did you get answer to this? same error showing up on specific servers for me, works fine on other servers.

    0
    Comment actions Permalink
  • Avatar
    Jason France

    Nope, I ended up writing a PowerShell script to get the CSV files and abandoned trying to do it with the Sisense Rest Connector

    0
    Comment actions Permalink
  • Avatar
    Conor Hennessy

    Hi Jason,

    I did a compare between my servers that it worked on and servers it didn't. The missing part was Sisense MongoDB OCBC Driver. When i installed this on the server with the issue/error it worked straight away,

    Sisense MongoDB ODBC Driver x64 v2.2.1.6 downloaded from here:

    https://documentation.sisense.com/latest/managing-data/connectors/mongo-db.htm

    Not sure why it needs this as it wasn't documented anywhere when setting up custom rest connector. I had it already installed on some servers for something else. It may not work for you and as you have developed alternative it may not be relevant but thought you might like to know.

    Conor

    0
    Comment actions Permalink
  • Avatar
    Jason France

    That might make sense, maybe the REST Connector is using the MongoDB to store the tokens or something...  I might have to give that a try.  Pretty sure I did not install the driver when I was testing...

    0
    Comment actions Permalink

Please sign in to leave a comment.