I found it was disabled, but as this field doesn't add any query, it should be allowed to be used.

CommentFileSizeAuthor
#3 Screen Shot 2017-11-02 at 2.04.02 PM.png40.99 KBgg24
#2 2915054-n2.patch635 byteshanoii

Comments

hanoii created an issue. See original summary.

hanoii’s picture

hanoii
Primary language Spanish
Location 🇦🇷UTC-3
commented
StatusFileSize
new 2915054-n2.patch635 bytes

Attached is a patch that enables support but make sure no aggregate function could really be used.

gg24’s picture

gg24 commented
StatusFileSize
new Screen Shot 2017-11-02 at 2.04.02 PM.png40.99 KB

Hi @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!

hanoii’s picture

hanoii
Primary language Spanish
Location 🇦🇷UTC-3
commented
Issue summary: View changes

@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.

purushotam.rai’s picture

purushotam.rai commented
Status: Active » Needs review

I think @hanoii is right here, we definitely need VFV to work in case of aggregation too.

  • hanoii authored 8e9ceaf on 8.x-1.x 
    Issue #2915054 by hanoii, gg24: Allow the field to be used on aggregated...
dawehner’s picture

dawehner
Primary language German
commented
Status: Needs review » Fixed

Thank you @hanoii, the explanation makes sense.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.