Canceling appointments through SOAP

[gdeyoung]

I have a page that shows the appointments booked to our conference rooms on our local intranet site. It pulls the appointments from the shared calendar of a generic user through a SOAP searchRequest.

Now I need add functionality to cancel appointments through this page, and I can't get a cancelAppointmentRequest to work. I've looked at cancelAppointmentRequests in the dev window of the zimbra client and the id numbers for the appointments don't look like any of the numbers I'm getting through my searchRequest.

The id in the cancel requests from the zimbra client are in the form of XXXX-XXXX and ids I'm getting through my searchresponse are much longer and in a totally different format.

Can someone tell me where and how I can find the proper id number that a cancelappointmentrequest is looking for?

[fmaguin]

Hi,

I have checked what is used as ids with CreateAppointmentResponse, SearchResponse and CancelAppointmentRequest.

CreateAppointmentResponse and SearchResponse will give you a invId to be used as id in CancelAppointmentRequest:
{"Body":{"CreateAppointmentResponse":{"invId":" 501-500", ...SNIP...

{"Body":{"SearchResponse":{"more":false,"sortBy":" dateAsc","appt":[{"uid":"..."
,"rev":900,"isOrg":true,"score":1.0,"inst":[{"s":...}],"id":"501","md":...,"name":"test"
,"fba":"B","invId":"501-500", ...SNIP...

<CancelAppointmentRequest xmlns="urn:zimbraMail" id="501-500"
comp="0"><m> ...SNIP...

HTH.

[gdeyoung]

Well, I thought that it was the invId that I was looking for. Unfortunately, my problem seems to be something else then.

Can someone explain why I get back different id numbers than I need for a CancelAppointmentRequest query when I run a SearchRequest query?

Here's an example appointment invId from a CreateAppointmentRequest sent from my zimbra client: 9610-9609 (These are the same ids used in the cancelAppointmentReqest)

Here's the appointment invId for the same appointment, from my SearchResponse: 41f86f55-ab26-4eb8-aa9a-fa685909d763:810-809

Why are the different, and what query do I need to run to get the invId in the correct format?

[fmaguin]

The string you are showing (41f86f55-ab26-4eb8-aa9a-fa685909d763:810-809) seems to be composed of a uid (41f86f55-ab26-4eb8-aa9a-fa685909d763) and an invId (810-809).

Could you post the body of the soap request/response ?
Which version are you using ?

Btw, you may have more answers to your problem in the developers forum.

[gdeyoung]

I've tried that, those last numbers (that look like an invId) aren't correct either.

Here's the body of my search request:

<soap:Body><SearchRequest xmlns="urn:zimbraMail" sortBy="none" limit="500" calExpandInstStart="1208351968000" calExpandInstEnd="1208438368000" types="appointment" offset="0"><query>inid:257 OR inid:258 OR inid:259 OR inid:260 OR inid:261</query></SearchRequest></soap:Body>

[fmaguin]

Looks like your timestamps are wrong... SNIP... nope, it's ok as seems Zimbra takes it in ms

I suppose you checked that the inid in the query elements are ok.

[gdeyoung]

Zimbra seems to like it's time in milliseconds rather than seconds, at least on our server. I don't know why that is, but that searchRequest returns the results I expect, apart from the wonky ID numbers.

[gdeyoung]

Thanks for your help, fmaguin.

It turns out that my issues were related to using the proxy account. I tried running my script locally using my own account and everything worked perfectly. I guess I'm going to have to create a way for users to log in through that page in order for canceling appointments to work.