Problem/Motivation
This is a support request, but I think could be useful for others as this should be a common example.
I'm trying to build a chart similar to this with the CHARTS module...

For this example, here is the build
One content type called "Cars". The Car node can be categorized by fields for both the "Brand name" and "Model type" (both fields are taxonomy terms reference fields).
I want to display a column chart showing the number of nodes (inventory, y-axis) for each "Model Type" grouped under the "Brand Name" on the x axis.
Tried aggregating in views, and read a ton of other posts... but no success.
What am I missing. Or is this functionality not possible???
Thanks!
Comments
Comment #2
andileco commentedHey, thanks for your question. One way to do this is create a parent view display and add two "Chart attachment" displays to your view. Each display would be filtered for one of "Sedan", "Coup", or "SUV". You'd want to have the parent display filtered for a model type that you'd expect to be present across all brands due to the way Views works. Does this help?
Comment #3
chucksimply commentedThank you for the quick reply @andeileco.
So my issue is the "Model Type" needs to be populated dynamically. I have let's say 50 different model types. BMW may have 3 of them, Mercedes may have 4 different types, and Audi... 5 that are totally different from the others.
I appreciate your suggestion, but I need more of a dynamic way to populate this part of the chart.
Any further ideas?
Thanks again!
Comment #4
andileco commentedThanks for reporting this... changing to a feature request and will be working on it soon.
Comment #5
chucksimply commentedAwesome! I look forward to this feature!
Comment #6
andileco commentedHave a patch for the 5.0.x branch, want to incorporate that first and then backport for 8.x-3.x if possible.
Comment #7
andileco commentedTesting the patch.
Comment #10
andileco commentedComment #11
andileco commentedI thought more about this...the solution is really to upgrade to 5.0.x (it doesn't make sense to apply this because in 8.x-3.x, we abuse the grouping option to represent stacking - 5.0.x fixes this). You'll get many more benefits by doing so too.