Chart configuration:

1. Chart Type: Table
2. Columns: SUM(Months_Left), SUM(Slope)
3. Rows: Site, ATTR(Curr_Svr_Nm), ATTR(Curr_Arch_Nm)

I've added the above table to my Dashboard. From the Dashboard, I want to sort the values in the SUM(Slope) column. Currently when you click the sort icon in the SUM(Slope) header, the table does not appear sorted. This is because this action will do a column level sort on the right-most Rows deck field, which is ATTR(Curr_Arch_Nm) in this scenario. In order to understand this behavior, you can think of the row headers as a hierarchical structure, with a branch for each value of "Site", and a sub-branch for each value of ATTR(Curr_Svr_Nm). Thus clicking the sort icon will sort the members of each sub-branch of ATTR(Curr_Svr_Nm). In this scenario, there's exactly 1 member per each sub-branch; thus there is nothing to sort.

What we really want to achieve in this scenario is to sort on the Site field, by the SUM(Slope) values.

The solution is to change the sort action to sort on the right-most, non-ATTR dimension field. This is the equivalent of doing an "Advanced" sort on the Site field, by the SUM(Slope) field. However, it is important to note that this is different from a column level sort when there are additional dimension fields to the left of the Site field. The column (or row) level sort will sort the members of each sub-branch, allowing each sub-branch to have a different ordering, where a field level sort will sort the possible values of the field by the selected measure values. In this scenario there is only 1 branch containing the Site values, and thus both the field level and column level sorts will produce the same result.

We will also support the same for the transposed scenario (ie the Rows and Columns fields swapped).