jon.nolan | 2024-03-05 16:00:15 UTC | #1
I'm attempting to pull conversation data for individual agents but I keep getting "The request failed with response code: 400. Message: invalid dimension value". Below is what I'm using to test with and I'm just not seeing what dimension value is incorrect based on my researching other topics on here. Below is the request.
{ "interval": "2024-03-03T22:00:00.000Z/2024-03-05T22:00:00.000Z ", "order": "desc", "orderBy": "conversationStart", "paging": { "pageSize": 25, "pageNumber": 1 }, "segmentFilters": [ { "type": "and", "predicates": [ { "type": "dimension", "dimension": "userId", "operator": "matches", "value": "USERID" }, { "type": "dimension", "dimension": "segmentType", "operator": "matches", "value": "interact" }, { "type": "dimension", "dimension": "segmentEnd", "operator": "notExists", "value": null } ] } ], "conversationFilters": [ { "type": "or", "predicates": [ { "type": "dimension", "dimension": "conversationEnd", "operator": "notExists", "value": null } ] } ] }
Jerome.Saint-Marc | 2024-03-05 16:09:24 UTC | #2
Hello,
The userId value is expected to be of GUID format: I mean something like "1415673f-2676-4b9c-8372-ae8930b68d6a" (8 characters, '-', 4 characters, '-', ...).
That's what the Genesys Cloud server is complaining about in the response (invalid dimension value for your userId).
Regards,
jon.nolan | 2024-03-05 16:25:39 UTC | #3
Well, dang it. Thanks for the quick response Jerome! That worked, don't know why I didn't realize that.
Jerome.Saint-Marc | 2024-03-05 17:00:43 UTC | #4
No problem. I didn't know myself it was checking format of some of the attribute values. So I've learned something new today :-)
system | 2024-04-04 17:01:36 UTC | #5
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 25018