Order piles within columns in report definition chart
Hi,
Using the piled up column chart associated with a report definition rule :
One of request's elements is a function grouping the retrieved data by urgency (GroupUrgency) and returning a string, namely 'P<20', 'P<40' or 'P>40'.
Data is ordered by "Agent" first and then by "Urgency" (min value to max value) :
We then use a conditionnal coloring on the GroupUrgency result for the piled up column chart and get the following result :
However, we wish to order the piles in each column as follow : green(P<20) at the bottom, then orange (P<40) and finally red (P>40) at the top.
For information, when switching the ordering to "Max value to Min Value" we get : orange (P<40) on top, green(P<20) in the middle and red (P>40) at the bottom.
Any idea(s) on how this ordering works, how to influence it and obtain the desired result ?
Thanks.
Pegasystems Inc.
US
I haven't seen any specific documentation on this particular functionality, but my impression from the stacked column charts I've worked with is that the order of the stack is the same as the order of the legend, and the order of the legend is the order that the series are added to the chart. Are you seeing something different from this?
Sopra-Steria
FR
Thanks, Ron.
I guess your observation is correct : the order of the legend seems connected to the order of the stacks; Green at the bottom then orange and finally red.
My first guess was that the order of these was probably linked to the quantities represented by each stack : the one with the most elements first (green) followed by red and orange. However, if I switch the order criteria to its contrary, the orange (the one with the least amount of values) stays on top, whereas I was expecting it to be at the bottom.
My second guess led me to believe the order might be based on the string I use for the grouping ('P<20'...). Thus I changed it for a simple 'A', 'B' or 'C' return :
Switching the ordering again gives me : C, A, B. So that's not it either.
Changing the order in which I enter the conditionnal coloring for the legend doesn't change a thing either : I always get "C, A, B " or "A,C,B".
After a few tests, my understanding is that the order of the stack in each column is actually based on the order of the stacks of the first column.
Thanks, Ron.
I guess your observation is correct : the order of the legend seems connected to the order of the stacks; Green at the bottom then orange and finally red.
My first guess was that the order of these was probably linked to the quantities represented by each stack : the one with the most elements first (green) followed by red and orange. However, if I switch the order criteria to its contrary, the orange (the one with the least amount of values) stays on top, whereas I was expecting it to be at the bottom.
My second guess led me to believe the order might be based on the string I use for the grouping ('P<20'...). Thus I changed it for a simple 'A', 'B' or 'C' return :
Switching the ordering again gives me : C, A, B. So that's not it either.
Changing the order in which I enter the conditionnal coloring for the legend doesn't change a thing either : I always get "C, A, B " or "A,C,B".
After a few tests, my understanding is that the order of the stack in each column is actually based on the order of the stacks of the first column.
Meaning that, if the first column doesn't have any elements for one the string values (here orange P<40), it only applies the order to the other two values (green P<20 and red P>40) and only once it encounters the third one (orange P<40) does it include it, just adding it at the end but the order already happened for the previous ones. Therefore, I can't obtain the order I want unless my first column has elements for each of the string values.
Does that seem like a possible hypothesis to you ? Any idea(s) on how to get around this mode of operation ?
Sopra-Steria
FR
The "solutions" I identified so far are :
- Ordering by "GroupUrgency" first then "Agent". Chart is ok but that messes up my table view by grouping by 'P<20'...etc. first.
- Ordering by "GroupUrgency" first then "Agent" but display the result as a matrix for the table view. This way I get the desired chart but a different table.
My goal was to obtain the chart I first described and a table first grouped by "Agent" then by "Group Urgency" as I implemented it in the first place. My understanding is that I can't get both at the same time. Correct ?
ASRC Federal
US
I have tried changing the legend order and must say I am really disappointed that this isn't something which is customizable.
Reporting isn't definitely PEGA's strong points especially in comparision to salesforce and this is one such pain point. Wish they improve on this in the future.