Skip to main content
I have created a stacked column chart to visually show the progression of a specific CTA's tasks by status (open/closed). In the chart, the Subject (or Task names) can only be alphabetized, not sorted to represent the order they appear in the playbook. We named our tasks starting with Task 1, Task 2, etc. to get around this, but I have 1 larger playbook that goes up to 10 tasks. Reports alphabetize Task 10 before Task 1. Are there any additional ideas to show these tasks in chronological order?
Hi Katie, I din't get the context exactly, could you please add a screen-shot for better understanding.

 This is the particular chart I mentioned. We named the playbook tasks Task 1, Task 2. etc. which typically allows us to 'alphabetize' in the same order as the playbook tasks, but in this case we have 10 tasks and 10 comes before 1 instead of after 9. It would be nice to have an option to either alphabetize OR keep the tasks in the order they appear in the playbook so we could remove the Task 1, Task 2 label and still keep them in chronological order.
Hi Katie, 





In latest release we have shipped Aliases, this would be possible with that. Please refer this article for more info.





For better understanding please refer below screenshot.











Always ready to help!
The alias is a good start, but it still does not give me the ability to manually reorder the columns, just to name the differently. Another example, I want to show a stacked column chart of our NPS scores...the chart orders the values: 0, 1, 10, 2, 3 etc. I want to see 0,1,2....9,10. 
Hi Katie,





Reporting follows alphabetical (in case of a string field) ascending or descending sort for the axis labels. So what you are seeing can be termed as expected behavior. Unfortunately, [i]Task 1[i]0 comes earlier than [i]Task 1[i]: [i](0 comes earlier than :) in most places. One potential resolution this to use the space after the number and before the ":" (Task 10 : , Task  1 : , etc ). Let me know if this works for you! 


 


While there are multiple ways to approach this problem, providing manual sort option does not seem like the most elegant solution. One way is for the reporting to understand the constructs present in other areas of the application and have a domain specific behavior. Currently, reporting works as a general purpose tool. We plan to enhance it with the domain knowledge as a part of our long-term roadmap. 



I like where Rakesh is going with this request. To me, this is less about how a Report sorts, and more about this specific Report (which is displaying Tasks) having the context that these Tasks generally appear within a specific order within a CTA. Thus, we end up with something very similar to a Sales funnel, whereby we're measuring how many CTAs have reached any specific point in the "CTA Journey".





A Report that is somehow aware of that funnel Context is definitely better than the work-around-y approach of naming the Tasks to force the order.

Reply


Terms & ConditionsCookie settings