Sorting issue with a custom column on a report.

[Jared_Mauch]

Workfront Community,

A report that uses a custom column to show the program name linked to projects isn't fully sorting like I had hoped. It's sorts programs sporadically. For example, Program A with be listed six times in a row, then Program B and Program C will each have some entries, and then Program A will show up again with more entries. I can't group off of this custom column in the groupings settings for the report, but am I able to edit the text mode that will allow all of Program A's entries to be listed together?

displayname=Program
linkedname=project
namekey=view.relatedcolumn
namekeyargkey.0=project
namekeyargkey.1=program:name
querysort=project:program:name
sortOrder=1
sortType=asc
textmode=true
valuefield=project:program:name
valueformat=HTML

[Kurt_Jones]

Jared, this looks like a project report?  In the groupings area you should be able to find Program Name as a choice to use for grouping which should put all the various programs together. 

[Jared_Mauch]

Kurt, it's actually a task report for finding tasks assigned to a user via a prompt. Program Name is column option that I can add to the report, but it is blank for all the entries when I add it. That's why the custom column was created. Is there something I can add to the text mode for the column to have entries grouped correctly by it?

[RitaCh1]

Hi Jared,

I am trying to sort the due date in the report column with the text formula:

linkedname=task
namekey=view.relatedcolumn
namekeyargkey.0=task
namekeyargkey.1=dueDate
sortType=asc
valuefield=task:dueDate
valueformat=atDate

sortOrder=1

Not sure it is correct or not and I am getting and error "APIModel INTERNAL does not support field sortByNaN (PortalSection)" & Invalid Parameter: Search Parameter value "null"

What is the correct formula I should use for getting the column sorted?

[skyehansen]

I see it's happening in my instance as well, which makes me feel like it's either a bug or intentional.

* To confirm, you can report it to Support and ask. 

* Workaround 1: you could sort it by program ID rather than program name. This should have a better result (keep the program stuff together) although it definitely won't go in alphabetical order by program name, at this point.

* Workaround 2: put a custom field on the project custom form to bring the program name down a level, so you're sorting at a closer level.

[RitaCh1]

Hi Jared, 

I am trying to sort the due date in the report column with the text formula:

linkedname=task
namekey=view.relatedcolumn
namekeyargkey.0=task
namekeyargkey.1=dueDate
sortType=asc
valuefield=task:dueDate
valueformat=atDate

sortOrder=1

Not sure it is correct or not and I am getting and error "APIModel INTERNAL does not support field sortByNaN (PortalSection)" & Invalid Parameter: Search Parameter value "null"

What is the correct formula I should use for getting the column sorted?

[Kurt_Jones]

Rita,

If your report is a task report the "due date" is the planned completion date.  Without using textmode (switch to Standard mode and make your field is planned completion date), you can go under Advanced Options and you'll see a sort option available and you can also rename the column to be Due Date instead of planned completion date if you wish

[kautuk_sahni]

@Jared_Mauch Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!

[Jared_Mauch]

Hi @kautuk_sahni,

The issue still persists. Using the Program ID would sort and list the entries as hoped, but since the ID is a string of characters rather than the program names, it made it difficult to know which program was which. It's when I go in text mode for the column and change programID to program:name where the entries are grouped and sorted in a sporadic fashion. Not all of the entries for program A are grouped together. There may be a few for program B and a few for program C before more for A are listed. It's interesting that using ":name" would cause this.