Grouping project report by requestor home team name | Community
Skip to main content
E
EricaLo
Level 3
October 21, 2021
Solved

Grouping project report by requestor home team name

  • October 21, 2021
  • 2 replies
  • 2109 views

I created a project report that is grouped by the Converted Request Originator's Home Team ID, and then I edited the text mode code to display the home team name instead of the ID, which worked. However, in the Summary tab, the data isn't broken out into separate sections by home team ID/name, it just says "No Value." I'd love to be able to display each home team and the number of projects submitted by each team here. Hoping someone can help! I've attached some screenshots of the report and the Summary tab, and here is the text mode code I used:

Grouping text mode by home team name:

group.0.linkedname=convertedOpTaskOriginator

group.0.namekey=view.relatedcolumn

group.0.namekeyargkey.0=convertedOpTaskOriginator

group.0.namekeyargkey.1=homeTeam

group.0.namekeyargkey.2=name

group.0.valuefield=convertedOpTaskOriginator:homeTeam:name

group.0.valueformat=string

textmode=true

    Best answer by skyehansen

    Honestly, this kind of thing is better if you just put it on the user object. One of the key tools for a system admin is to apply a custom form to all user profiles. This Home Team Name field would go on that user form and hopefully the calculated field is very easy to build on that user form.

    After you apply this to the user, you'll find that the calculated field is then available for you in the converted issue originator list of fields.

    Why it's a key tool -- As a side effect of putting it on the user, it's also available in a lot of other reporting areas, e.g. project owner home team, task assignee home team, etc. Whereas if you put it on the request form itself that doesn't help anything except for the request form in that workflow. As a bonus for your particular use case, the information does not need to be updated across existing forms.

    @Kyna Baker - inactive‚ #quick-tip-idea + what are the most useful fields to put on a user profile?

    2 replies

    imgrund
    Adobe Employee
    imgrundAdobe Employee
    Adobe Employee
    October 21, 2021

    Hi - unfortunately, once you change the groupings in text mode, you can't use the summary tab or charts. :(

    Hoping someone has a solution for you for what you have now.

    Something to help in the future (and sorry you can't do this retroactively), but on the original request, have a calculated field that captures the Owner.Name and Owner.Home Team.Name. Then on the project form, put those same calculated field on but leave the formula blank. When you convert from request to project, the value that populated the request will move to the project form as well.

      E
      EricaLoAuthor
      Level 3
      October 22, 2021

      Thanks Anthony! I think I'll go ahead and try this method out. I'm a bit rusty on creating calculated fields. If I wanted to display the "converted request originator"s home team name, do you know what text I'd use in the calculated field? I've been scouring Workfront's documentation but I can't find any resources on basic calculations like this.

      imgrund
      Adobe Employee
      imgrundAdobe Employee
      Adobe Employee
      October 22, 2021

      Unfortunately, I do not know how to do that. That is why I mentioned I've done the calculated field on the request and transfer that info during conversion. :(

      Fingers crossed someone knows how to get o Converted OpTask Originator into a project calculated field.

      RandyRoberts
      Community Advisor
      RandyRobertsCommunity Advisor
      Community Advisor
      October 25, 2021

      Thanks Skye, we have a form on every user object with home office, employee ID, available PTO, manager name, manager hierarchy, department/business Unit, and check boxes for company trainings they've attended. This has been incredibly helpful for situations such as the OP's.

      I would encourage everyone to implement this.

      Terms & ConditionsAccessibility statement

      Loading footer...