Unfortunately, if you search for a list of options in a multi-value contact custom field, the default implementation looks for a contact that has all of the values, instead of any of the values. Unfortunately there is also no workaround (in APIv3) since the or API option is not implemented for the Contact entity.
For RemoteContact we want to implement this feature anyway, with the following approach:
we add a new API option called multivalue_search_mode_or, which lists any number of multivalue custom fields that should be treated as an OR-based search.
the implementation will run only this search in SQL and restrict the original query to the resulting (contact) IDs, before handing the rest of the query over to the API
Unfortunately, if you search for a list of options in a multi-value contact custom field, the default implementation looks for a contact that has all of the values, instead of any of the values. Unfortunately there is also no workaround (in APIv3) since the
orAPI option is not implemented for theContactentity.For
RemoteContactwe want to implement this feature anyway, with the following approach:multivalue_search_mode_or, which lists any number of multivalue custom fields that should be treated as anOR-based search.