Santiago_Carrillo | 2019-02-11 21:31:54 UTC | #1
Good afternoon,
It turns out that to know the path in the IVR through which the different calls enter, we decided to assign them a wrapUpCode according to the options they select. At the time of entering the API to obtain information, a couple of problems emerged (in conversation aggregate):
1 - When I consult this information in aggregate conversations, I search for id, but there are certain wrapupcodes that do not generate the metric for this query, which is tIvr, it only extracts the information from the nError metric, but I need that in all cases I bring the metric tIvr and I do not understand what the problem is, I do not see that I am doing wrong the procedure according to the documentation and the logic itself in general.
Request
Response
2- the metric tIvr in count shows me the number of records that are associated (in this case the number of records with certain wrapUpCode), but when I compare it with a more detailed count in the interaction screen with the records that are shown, the Results in terms of quantity are similar but not the same, so why is not the API returning the total number of real calls, which I believe is the one that appears on the interaction screen, which is not taking into account?
In this evidence it can be seen that even though the totalized result is 200, we go to the interaction screen and the result is higher, given that we are on page 5 of the pager, taking into account that each page has 50 records, Obviously there are more than 200 records. I am taking into account that sometimes on this screen records are taken some time before and after the filter, but as you can see, I simulate exactly that time from the lowest date to the highest date, and the indicator it continues without being precise.
I appreciate the goodwill in advance.
The client is pressing for this information.
I appreciate the attention provided.
tim.smith | 2019-02-11 21:59:14 UTC | #2
Missing, incomplete, or incorrect data results from the API cannot be investigated via the forum. Please open a case with PureCloud Care to investigate.
system | 2019-03-14 21:59:16 UTC | #3
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 4562