Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

CLI Issues quality evaluations query list

  • 1.  CLI Issues quality evaluations query list

    Posted 06-05-2025 18:32

    Pat_Johnson | 2024-09-05 17:02:25 UTC | #1

    Anyone else having issue with gc quality evaluations query list --conversationId "ID"

    I get this error

    { "message": "Maximum number must be greater than or equal to 1", "code": "bad.request", "status": 400, "contextId": "8dc13918-e596-4e4b-90e8-33ccd75f1200", "details": [], "errors": [] }

    When I use the API with Powershell IT works

    $WebRequestParams = @{ Uri = "https://api.usw2.pure.cloud/api/v2/quality/evaluations/query?conversationId=ID" Method = "Get" Headers = @{ "Authorization" = $Token "Content-Type" = "application/json" } } $Request = Invoke-WebRequest @WebRequestParams | ConvertFrom-Json $Request.entities

    John_Carnell | 2024-09-09 12:43:16 UTC | #2

    Pat_Johnson, post:1, topic:28918, full:true
    Anyone else having issue with gc quality evaluations query list --conversationId "ID"

    I get this error

    { "message": "Maximum number must be greater than or equal to 1", "code": "bad.request", "status": 400, "contextId": "8dc13918-e596-4e4b-90e8-33ccd75f1200", "details": [], "errors": [] }

    When I use the API with Powershell IT works

    $WebRequestParams = @{ Uri = "https://api.usw2.pure.cloud/api/v2/quality/evaluations/query?conversationId=ID" Method = "Get" Headers = @{ "Authorization" = $Token "Content-Type" = "application/json" } } $Request = Invoke-WebRequest @WebRequestParams | ConvertFrom-Json $Request.entities

    Hi Pat,

    Thats unusual. I will open a ticket with my team and investigate further.

    Thanks, John Carnell Director, Developer Engagement

    Pat_Johnson | 2024-10-02 14:16:29 UTC | #3

    any updates on this?

    John_Carnell | 2024-10-02 15:21:33 UTC | #4

    Hi Pat,

    It's still in our backlog. We are working through some higher priority issues and will get to it.

    Thanks, John Carnell

    system | 2024-11-01 15:22:08 UTC | #5

    This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

    Jerome.Saint-Marc | 2024-11-12 13:57:40 UTC | #6

    Hello,

    Apologize for the delay. This should now be solved in the latest CLI SDK 116.0.0. The CLI client used to set 0 as a default value for integer parameter, when not specified as command parameter. It is now fixed.

    Regards,

    This post was migrated from the old Developer Forum.

    ref: 28918



Related Content