Module Description
This project provides two different views filters to allow database fields to be compared.
The first filter will allow two different fields to be compared using the standard comparison operators (<, =, >, <=, !=, >=).
The second filter will allow a field value to be checked against another multi-valued field with the operators of "contained in" or "not contained in".
These filters will only work on views displays that use fields, as the chosen left and right fields will need to be specified in the list of fields (although they may be hidden if necessary).
This module is based on dench0's sandbox module from 2016: Views fields comparison, but has been extended to provide the "contained" filter.
The "contained" filter now works with fields attached to different entity types, and neither field needs to be attached to the base entity type of the view. No check is made on field type, but it obviously does not make much sense to have a filter looking for a text value contained in a multi-valued numeric field.
If you encounter an error with table aliases generated automatically by views, then you will need to apply the Drupal core patch from this issue: Identifiers longer than 63 characters are truncated, causing Views to break.
The first filter will allow two different fields to be compared using the standard comparison operators (<, =, >, <=, !=, >=).
The second filter will allow a field value to be checked against another multi-valued field with the operators of "contained in" or "not contained in".
These filters will only work on views displays that use fields, as the chosen left and right fields will need to be specified in the list of fields (although they may be hidden if necessary).
This module is based on dench0's sandbox module from 2016: Views fields comparison, but has been extended to provide the "contained" filter.
The "contained" filter now works with fields attached to different entity types, and neither field needs to be attached to the base entity type of the view. No check is made on field type, but it obviously does not make much sense to have a filter looking for a text value contained in a multi-valued numeric field.
If you encounter an error with table aliases generated automatically by views, then you will need to apply the Drupal core patch from this issue: Identifiers longer than 63 characters are truncated, causing Views to break.
Module Link
Project Usage
315
Security Covered
Covered By Security Advisory
Version Available
Production
Module Summary
This module aims to solve the issue of comparing database fields in views displays using different comparison operators and checking field values against multi-valued fields.
Data Name
views_field_compare
OPENAI CHATBOT
OPENAI CHATBOT
