I keep getting an error ("trying to get property of non-object in std:class" or something) when using aggregation in the views UI.

But that's not even really my issue, seeing as views already has aggregation functionality for fields is this column in the graph settings even really necessary?

Comments

asherry’s picture

asherry CreditAttribution: asherry commented

The aggregation setting on views changes the query group on all fields, even if you only want the aggregation settings to group on one. I put in the aggregation so that you could get a visualization working without having to enable views aggregation, to make it simpler.

Could you post a little more info about your view configuration? I could have a look.

strainyy’s picture

strainyy CreditAttribution: strainyy commented

Thanks for the response Asherry.

My views configuration is really basic. A few fields, AJAX enabled, a filter in a block. It works fine until I set any aggregation option in the settings of the D3 Visualisation format.

asherry’s picture

asherry CreditAttribution: asherry commented
Assigned: Unassigned » asherry
asherry’s picture

asherry CreditAttribution: asherry commented
Status: Active » Closed (outdated)

Since the aggregation functionality has changed quite a bit I'm going to mark this as outdated. If this exact error is still happening then feel free to re-open, otherwise any new bugs deserve separate issues.

And the question about if the aggregation is needed at all is still a valid one, but since the views aggregation changes the field config and the query pretty heavily, I'm still going to say that it's sometimes much more lightweight to have the views display handler do the aggregation.