Ordering Aggregate Data Models for use in Chart Components

Questions
1

I have a chart component that shows customers and volumes. I am using an aggregate model to present these totals, but I am unable to figure out a way to sort in order to get it to display in descending order, with largest on top. Because the aggregate only exists in the model, I can’t use it to order by, and ordering by non-aggregated totals doesn’t give me the correct order.

Any ideas for me Skuid Community?

Current chart, no particular order.

image
image979×321 37.8 KB

2

SOQL accepts aggregate functions in the order by clause. It looks like your field is something like GCNetWeightCaseLac. You should be able to add SUM(GCNetWeightCaseLac) DESC to the “fields to order by” property on the general tab of the model definition.

See below an example of ordering opportunity aggregation by amount.

Screen Shot 2022-04-20 at 11.17.38
Screen Shot 2022-04-20 at 11.17.381844×682 57.2 KB

4

Hey Rob! I tried this out, and although it appeared to do good things and change the order of my chart, I’m still seeing some strange behavior.’

When I add a ‘DESC’ property to my ‘fields to order by’ on my model, the order does change, but it doesn’t end up in DESC order on the chart, it’s just different. It also continues to include a ton of lines, but only displays every third label.

Model with condition:

image
image1788×275 31.5 KB

Chart with Model driving it:

image
image1265×837 46.8 KB

Resulting chart:

image
image942×313 33.5 KB

Any direction would be appreciated, but I do think we’ll end up moving this piece into a Tableau visualization for now.

Best

Chris

5

Here are some guesses.

  1. I think you have more groupings than just Customers on the model. If you put the model into a table - you will find that the sort by Sort_net_weight.... is in fact getting applied to the model, but that other grouping items are getting in the way.
  2. Then when the chart builds it processes those rows in order as they appear in the model, but when another row is found for a prior customer the additional value is thrown up into that prior segement. This is how the volumes get “unsorted” in the exhibit.

Finally - Our chart components start eliminating axis labels when there are too many rows. You might add a model limit to show top 10, or you might expand the chart height to ensure that all the axis labels show.

PS - I really don’t think you need to go to Tableau for this. Thems fightin words… :sweat_smile:

6

Bingo! I cleaned up my groupings (which I originally thought were necessary to power the axis) and I’m in business. Once I reduced down to 10 records, all labels show. Ultimately I’d like to have a way to increase the default height to include additional records, but this does indeed make Tableau unnecessary - apologies for the unintended slight! :grimacing:

7

No appology necessary. Tableau and similar BI tools do have thier place. They have richness and features we don’t offer…

You can increase the default height on the display properties of the chart. But I don’t think you can make that dynamic to the number of records you want to show.

Have a great weekend.