noraz123 | 2021-05-03 19:32:10 UTC | #1
We are building an integration with PureCloud, and want to pull in a subset of calls based on Queue.
One of our clients has about 250 queues, of which about 200 are the ones we'll work with.
Are there any concerns with how many filters we can apply or is there anything more scalable?
For example, here is our code with filters for two queues. We are calling the endpoint /api/v2/analytics/conversations/details/query (or are testing with this, will likely use an asynchronous job when done) "segmentFilters": [ { "type": "or", "predicates": [ { "type": "dimension", "dimension": "queueId", "operator": "matches", "value" : "7f5fc4e4-e631-414d-b83d-f2d39df3da88" }, { "type": "dimension", "dimension": "queueId", "operator": "matches", "value" : "55bfa0e6-752a-4df5-bfd9-54e115fe206f" } ] } ]
As it stands, we could end up having 200 filters in our "OR" predicates sections.
Any concerns?
anon11147534 | 2021-05-04 16:28:02 UTC | #2
Hi,
Yes, your solution is correct. The way that filter predicates have been implemented in this API can sometimes result in large queries. There should be no issue with a query containing 200 or more filters.
noraz123 | 2021-05-04 23:06:48 UTC | #3
Great, thanks for the confirmation.
system | 2021-06-04 23:06:51 UTC | #4
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: 10802