Need workaround for inability to sort A/Z on pick lists in Reporting. | Community
Skip to main content
R
Ryan_McGee
Level 5
October 29, 2020
Question

Need workaround for inability to sort A/Z on pick lists in Reporting.

  • October 29, 2020
  • 1 reply
  • 379 views

Here's our use case: we have custom forms from which a PM can select a writer and a designer from a pick list in a project. We can bring that column into a project report, but we can't sort on these columns. Everything else (start date, project name, etc) sorts fine and dandy.

In reading up, it looks like Workfront overtly forbids A/Z sorting from pick lists. I'm wondering 1) am I reading this correctly and 2) how have people worked around it? I supposed I could try some slick text mode work and bring in task assignments into the Project report, but want to see what others have done.

Thanks!

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    1 reply

    KatherineLa
    Community Advisor
    KatherineLaCommunity Advisor
    Community Advisor
    November 2, 2020

    Hi Ryan,

    I'm tinkering at the moment, and I seem to be able to sort on picklist values normally unless the picklist is ALSO a multi-select type. Those definitely have greater limitations, I'd suspect the data is stored in such a way that it would make it hard to add those extra features. So first - is the picklist you're referencing one that allows multiple choices?

    If so, does it have to be? Could you make it two lists that required one choice each? You could potentially recombine them in reporting if you wanted to display that way.

    If it needs to remain a multi-select, is the list small enough that creating another set of fields that populate based on those choices a viable option? IE if you have 6 people listed, then it would be possible albeit annoying to create another set of fields that change depending on what's selected in the original picklist. Those fields could then be used in reporting to sort on.

    The second option is viable if the number of choices is limited and relatively static. If it's long or highly variable, then you may be setting yourself up for a maintenance nightmare.

    Katherine

    Terms & ConditionsAccessibility statement

    Loading footer...