Solved: API doc error? about lstrecordaccessDetailHistory

shkuzu · ‎12-01-2016

Hi,

I check the API doc and test it.

In the doc, here is the example query

<body>

<bodyContent xsi:type=

"java:com.webex.service.binding.history.lstrecordaccessDetailHistory">

<recondID>5862</recondID>

<timeZoneID>4</timeZoneID>

</bodyContent>

</body>

I found "lstrecordaccessDetailHistory" is not correct, it should be "LstrecordaccessDetailHistory".

Because lstrecordaccessDetailHistory shows not class found error.

When I use Lstxxxx method, then I see "sorry, no record found" error.

After that, I noticed the attribute of recording ID is "recondID" in the doc.

So I guess it is a typo. then I changed it to recordID.But it still shows "no record found".

I noticed LstRecording use not "recordID" but "recordingID".

So I use "recordingID" instead of recordID.But it shows another error

unable to find FieldDescriptor for 'recondingID'

Could you give me your example to see recording detail history?

ryanhunt · ‎12-01-2016

Historical data typically takes 48-72h before its accessible; unfortunately its not realtime.. have you allowed enough time for this?

ryanhunt · ‎12-01-2016

Historical data typically takes 48-72h before its accessible; unfortunately its not realtime.. have you allowed enough time for this?

shkuzu · ‎12-01-2016

Ryan, Thank you.

You are correct. it does not take enough time.

Do you know which is correct recordID or recondID?

ryanhunt · ‎12-02-2016

It should be recordID, its a typo I'll see if we can get fixed.

shkuzu · ‎12-04-2016

Hi Ryan,

Thank you.

I still see "Sorry, no record found". It took more than 48 hours.

I used value of recordingID as recordID

The recordingID is returned by "lstRecordingResponse"

return of lstRecordingResponse

Are something wrong?