• Replies 5 replies
  • Subscribers 71 subscribers
  • Views 181 views
  • Users 0 members are here
Related

C# SDK - Creating a Session with the BatchFacade

Former Member
Former Member $organization

Greetings ,

I am trying to using the BatchFacade in the C# SDK to create a session and then log that session in as our anonymous user. I can see how a developer can use the BatchFacade to do this. Seems fairly straightforward to me. 

I kept getting an error in my batch and isolated it down to creating a Session through the BatchFacade. Assume that tessituraService is already instantiated and credentialed:

 SessionRequest sessionRequest = new SessionRequest() { IpAddress = String.Empty };
 BatchResponse batchResponse = await tessituraService.BatchFacade
     .With(tessituraService.BatchFacade.Web.Session.CreateSession(sessionRequest))
     .Call();

The batch fails and I get the Error message: 

"Object of type 'Newtonsoft.Json.Linq.JObject' cannot be converted to type 'Tessitura.Service.Client.Web.SessionRequest'."
Copying and pasting my payload into the REST Client (taking the SDK out of it) yields the same results. I've xx'ed out the domain below for security purposes.
    {
  "Requests": [
    {
      "Id": 1,
      "HttpMethod": "POST",
      "Uri": "http://xxxxx/TessituraService/Web/Session/",
      "ContinueOnError": false,
      "Content": {
        "IpAddress": "",
        "BusinessUnitId": 0,
        "Organization": null
      },
      "DependsOnRequests": null,
      "ReturnTypeString": "Tessitura.Service.Contract.SessionResponse"
    }
  ]
}
When I create a session through the SDK without the BatchFacade, it works as expected. Is there something I'm doing wrong here or is this an exception error in the REST application? Thanks once again for the time and the help!
 
Parents
  • Former Member
    Former Member $organization

    Just taking a step back here... The original premise of this is to log in the Anonymous web user using a batch call. In reading the past help documentation it's been the recommended practice to have an anonymous web user and log that user in before transacting on the web. In shifting the the REST API, this is still a necessary practice? I would assume so since the user will have a cart and could potentially be reserving seats with that anonymous account. Did want to ask that up-front though. I am assuming we will uncover the answer to this as we continue to work on REST integration. Any insight here is appreciated. Thanks as always.

  • $organization in reply to Former Member

    Hi Randolph,

    Anonymous users are no longer needed with REST API as you can add items to your basket without being logged in. All information can be saved to the cart using constituent 0 and transferred to the constituent once they've logged in as before.

    There is also a new feature in V14 loginAsGuest Web/Session/{sessionKey}/LoginAsGuest this new method allows you to log in a customer using just their email and so they can complete a transaction without creating an account. If the email matches an email on the system it will use that account to make the order. For security guest login does not give access to personal information on the account but it is still pretty useful for quick sales. 

Reply
  • $organization in reply to Former Member

    Hi Randolph,

    Anonymous users are no longer needed with REST API as you can add items to your basket without being logged in. All information can be saved to the cart using constituent 0 and transferred to the constituent once they've logged in as before.

    There is also a new feature in V14 loginAsGuest Web/Session/{sessionKey}/LoginAsGuest this new method allows you to log in a customer using just their email and so they can complete a transaction without creating an account. If the email matches an email on the system it will use that account to make the order. For security guest login does not give access to personal information on the account but it is still pretty useful for quick sales. 

Children