Hi,
Thank you very much for the reply.
I do not know if this behavior is expected, but I tested EQ with only a single value, and it returns the entity in the result.
{
"limit": 100,
"after": 0,
"filterGroups": [
{
"filters": [
{
"propertyName": "hs_all_contact_vids",
"operator": "EQ",
"value": "201"
}
]
}
],
"properties": [
"id",
"hs_all_contact_vids",
"testenumeration"
]
}
{
"total": 1,
"results": [
{
"id": "251",
"properties": {
"createdate": "2022-09-22T04:02:01.807Z",
"hs_all_contact_vids": "201;251",
"hs_object_id": "251",
"lastmodifieddate": "2023-03-28T08:34:35.433Z",
"testenumeration": "Option1;Option2;Option3;Option4;Option5Option"
},
"createdAt": "2022-09-22T04:02:01.807Z",
"updatedAt": "2023-03-28T08:34:35.433Z",
"archived": false
}
]
}
I also tested the following, but none of them worked:
"value": ["201;251"] -> Invalid input JSON
"value": ["201"] -> Invalid input JSON
"values": ["201"] -> operator EQ requires a value
> For your use case, are the contacts who have multiple values for “hs_all_contact_vids” contacts who’ve been merged?
Yes. The problem can also be reproduced if using a custom property that allows selecting multiple options (Multiple checkboxes).
{
"limit": 100,
"after": 0,
"filterGroups": [
{
"filters": [
{
"propertyName": "testenumeration",
"operator": "EQ",
"value": "Option1"
}
]
}
],
"properties": [
"id",
"hs_all_contact_vids",
"testenumeration"
]
}
{
"total": 2,
"results": [
{
"id": "151",
"properties": {
"createdate": "2022-09-20T12:29:20.903Z",
"hs_all_contact_vids": "151",
"hs_object_id": "151",
"lastmodifieddate": "2023-03-28T09:11:00.233Z",
"testenumeration": "Option1"
},
"createdAt": "2022-09-20T12:29:20.903Z",
"updatedAt": "2023-03-28T09:11:00.233Z",
"archived": false
},
{
"id": "251",
"properties": {
"createdate": "2022-09-22T04:02:01.807Z",
"hs_all_contact_vids": "201;251",
"hs_object_id": "251",
"lastmodifieddate": "2023-03-28T08:34:35.433Z",
"testenumeration": "Option1;Option2;Option3;Option4;Option5Option"
},
"createdAt": "2022-09-22T04:02:01.807Z",
"updatedAt": "2023-03-28T08:34:35.433Z",
"archived": false
}
]
}
It seems to me that the API is treating each value as a sub-field of its own even though GET returns them as one semicolon separated list. So, “EQ value” for enumeration types works like ‘retrieve all records that have at least this value in that property’.