we have created several custom_fields for a person and not all of them are filled for every contact. When I search for a person the response for the custom_fields look like this:
there is no id in order to distinguish from which field this data is coming. I really can’t understand why or what the API dev team was thinking when they left out the id of the custom_field. Is it really a big problem to make it like:
thanks for your reply! I think there is a misunderstanding. I know how the grab the ids of personFields but my problem is about the response you get if you run GET/persons/search and there the values of all custom_fields are returned without any way to find out to which personField the returned custom_fields value is associated.
Any update on this? It’s well past the six months, and it’s still not right. Consequently, another request is required for each returned item in order to get any reliable data from the search results.
This issue still exists and it’s also in the new v2 version. Would be lovely if the search would return the keys, same way as it does when getting contact by id