ssteiner | 2023-09-27 13:46:46 UTC | #1
when I list available groups (GET /api/v2/groups), I get 33 groups in my tenant. The groups have two distinct naming conventions. Some are called 'Customer xyz abc'. these I can search for with name startswith - here's the json content I'm sending (sending as POST /api/v2/groups/search
{"query":[{"type":"STARTS_WITH","value":"Customer","fields":["name"]}]}
The other groups' names starts with 'DE_BDE'. These I never get back using the search API. There's also another group having an underscore in the name that I cannot search for. am I missing something? Do I need some special encoding of the underscore character? I tried urlencoding (replacing _ with %5F) but no joy.
Eos_Rios | 2023-09-27 14:09:20 UTC | #2
I have a similar prefix but mine works as expected;
{
"query": [
{
"fields": [
"name"
],
"type": "STARTS_WITH",
"value": "Chronics_Defects"
}
],
"sortOrder": "ASC",
"pageSize": 10,
"pageNumber": 1
}
Are the groups you're not seeing not public by chance?
ssteiner | 2023-09-27 14:19:56 UTC | #3
Yep, it seems the groups I can't search have visibility = members. But the groups are all returned when I list them. I found an older article (in fact before posting here) that mentions an issue with search and visibility, and it's from 2017 and I figured the issue would've been addressed by now.
Even if I'm not supposed to see the groups, search and listing should be consistent.
tim.smith | 2023-09-27 14:27:23 UTC | #4
quote="ssteiner, post:3, topic:22243"] I found an older article (in fact before posting here) that mentions an [issue with search and visibility, and it's from 2017 and I figured the issue would've been addressed by now. [/quote]
The fix for that issue was deployed on January 26th, 2017.
ssteiner, post:3, topic:22243
Even if I'm not supposed to see the groups, search and listing should be consistent.
Please report this discrepancy betweent he endpoints via a case with Care. We do not have access to your org's data to verify this result and bug reports have to be processed through Care.
ssteiner | 2023-09-28 08:36:56 UTC | #5
little problem here with that: I'm not my customer's Genesys partner. So i requested access, and the best thing Genesys will grant me (contingent on the customer's Genesys partner agreement - not sure if that'll get me read access to all their cases and they'd probably not be too happy with that) is read-only access.
tim.smith | 2023-09-28 14:33:49 UTC | #6
You'll need to work with your customer's Genesys partner to get a case opened. This is not something we can do for you.
system | 2023-10-29 14:34:45 UTC | #7
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: 22243