Skip to content

[Views integration] Assume api.filter defaulting to 1 for fields to be used as filters

jensschuppe requested to merge jensschuppe/cmrf_core_d8:cmrf_views_filters into 8.x-dev

The Views integration only allows Views filters be added for fields that have api.filter explicitly set to 1 in the getfields API call response.

I can't, however, find any CiviCRM core entity field returning this flag, except for one, where it is being set to 0. Since documentation seems missing for api.filter, I assume its default is 1 and should thus be handled that way by CiviMRF Views.

Otherwise, no Views filters can be added for any field.

Merge request reports