Genesys Cloud - Main

 View Only

Sign Up

  Thread closed by the administrator, not accepting new replies.

  • 1.  Filter by "value *contains* substring" in Purecloud Platform API query?

    Posted 10-29-2019 15:49
    No replies, thread closed.
    Me and colleague have been hunting around for this to no avail.

    We are using very basic Platform API call under /api/v2/analytics/conversations/details/jobs for conversation detail query,

    {
    "interval": "2019-10-18T00:00:00.000Z/2019-10-19T00:00:00.000Z",
    "segmentFilters": [
    {
    "type": "or",
    "predicates": [
    {
    "dimension": "subject",
    "value": "Joe"
    }
    ]
    }
    ]
    }

    This searches for conversations on 10/18/19 where the subject field is exactly "Joe", i.e. emails with subject title "Joe".  So far so good.

    What we would very much like is a way to query for conversations where the subject field *contains* a substring such as "Joe".  In many programming languages this is usually represented as wildcard symbol * in the string or a like() function or contains() function, but none of these appear to work for Purecloud Platform API queries.  Is there a method for this in Purecloud Platform API?  Any help would be appreciated.
    #Integrations
    #Reporting/Analytics

    ------------------------------
    Scott Lipton
    InterWorld Highway
    ------------------------------


  • 2.  RE: Filter by "value *contains* substring" in Purecloud Platform API query?

    Posted 10-29-2019 16:52
    No replies, thread closed.
    I don't know of a way to do a wildcard search. You might get an answer if you post on the Developer Forum at https://developer.mypurecloud.com

    ------------------------------
    George Ganahl GCP (PureCloud) ICCE CCXP
    Principal Technology Consultant
    Genesys
    ------------------------------

    Original Message


  • 3.  RE: Filter by "value *contains* substring" in Purecloud Platform API query?

    Posted 10-30-2019 09:44
    No replies, thread closed.
    Ok, thanks.  Looking around, I found that query for user search does indeed have a "type" option for "CONTAINS", but the same doesn't exist for conversation query, so I'm pretty sure there's no way to wildcard.  We'll have to find a workaround another way.

    ------------------------------
    Scott Lipton
    InterWorld Highway
    ------------------------------

    Original Message


Related Content