Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I found it was disabled, but as this field doesn't add any query, it should be allowed to be used.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | Screen Shot 2017-11-02 at 2.04.02 PM.png | 40.99 KB | gg24 |
| #2 | 2915054-n2.patch | 635 bytes | hanoii |
Comments
Comment #2
hanoiiAttached is a patch that enables support but make sure no aggregate function could really be used.
Comment #3
gg24 commentedHi @hanoii,
I tried the above patch for the issue mentioned. I am able to reproduce the issue and the patch applies cleanly but after applying the patch when I check the aggregation types for that field I see only Group results together in the option list, no other aggregation options are available there. Attaching a screenshot as well. Please check.
Thanks!
Comment #4
hanoii@gg24 yes, that's on purpose. I mentioned exactly that on #2. Aggregation makes sense on SQL query, this is a compound field that pulls data from other views, so there's no true SQL aggregation function that will work here.
The patch only allows the field to be used on an aggregated query, but you can't apply any aggregation function to this field.
Comment #5
purushotam.rai commentedI think @hanoii is right here, we definitely need VFV to work in case of aggregation too.
Comment #7
dawehnerThank you @hanoii, the explanation makes sense.