Pulling "topic group" into a report

Hi Rani, I'd like you to have a look at the "https://wf-pro.com/textmode/api/">WFPro Text Mode catalog, where you'll find various examples that will give you an idea of the syntax for different views. In your case, you'll want to use the following in your column to jump up one level and grab the topic group name: valuefield=queueTopic:parentTopicGroup:name valueformat=HTML displayname=Parent Topic Group Regards, Narayan

That did it, thank you so much, Narayan! I really appreciate the super quick response. I'll take a look at the catalog you provided as well. That should be very helpful. Thanks again, Rani Rani Paul One &All

Hi Rani, While I expected the following in the prompt to work, it didn't and I can't sort out why. queueTopic:parentTopicGroup:name=Strategy&queueTopic:parentTopicGroup:name_Mod=cicontains Instead, you might want to add the following calculated field to a "standard" issue custom form that you attach to all of your issues: Name : Request Topic Group Name Format : Text Calculation : IF(ISBLANK(Request Topic Group Name), Queue Topic.Parent Topic Group.Name, Request Topic Group Name) This will store the topic group name and, should the topic group ever get deleted, will retain the old value. From here, you then gain the ability to group, filter, etc. on this value. In fact, I've done the same with the Queue Topic Name because these get deleted sometimes. Let us know how it turns out! Narayan

Thank you so much, @Narayan Raum ! This worked great! I now have the topic group as a prompt, yay. So cool. There was one strange thing that happened. I couldn't get the suggested calculated field to work at first; WF kept telling me that it was an invalid expression. So after trying all manner of combinations unsuccessfully I tried putting just IF(Queue Topic.Parent Topic Group.Name=="Strategy","Strategy","Digital Media") instead. That worked and allowed me to save the form. I went to the request form and submitted a few entries and it worked fine, but I was a little concerned about what you had mentioned, if we ever add more topic groups this wouldn't be an ideal construction. So just a few minutes ago I went back and pasted your recommendation in: IF(ISBLANK(Request Topic Group Name), Queue Topic.Parent Topic Group.Name, Request Topic Group Name) . And this time WF accepted the calculation, allowed me to save the custom form, and when I tested it on the form and report prompt it worked perfectly! I don't know if it was just that WF didn't recognize the new "Request Topic Group Name" field name until it had a few entries in it or what, but just thought I would mention that here in case anyone has a similar issue at first. So in summary, your solution works perfectly. I really, really appreciate your help!! Best, Rani Rani Paul One &All

Hi Rani, I suspect you've hit a common but subtle gotcha: when you create a new calculated custom parameter (e.g. Request Topic Group Name) and add it to a form, before attempting to refer to that new custom parameter itself in the formula (as in Narayan's solution on this one) you need to save the form first so that Workfront is aware that the new parameter exists, and then -- once it's "real" -- you can use it in the formula. Fortunately, it's only for these types of self-referencing formulas, and is easy to avoid once you know about it. Regards, Doug Doug Den Hoed - AtAppStore Got Skills? Lend a hand! https://community.workfront.com/participate/unanswered-threads

Rani, don't feel bad. This gotcha tripped me up again today. I'm glad it worked out! Thanks for the assist, Doug. Narayan

Hey all, Something fun to note, when referring to filters and prompts , ID and Name will reference the same area in the database, regardless of if you enter the GUID or the name of the object you're referencing. In other words, for the prompt to work, just reference parentTopicGroupID next time, and just make sure to set the label as "Topic Group Name" (or whatever you'd like.) This is not the case with views and groupings, ID will reference the GUID in those scenarios. Thanks! Dustin Martin Assigned Support Engineer Workfront

Hi Dustin, Just what we needed to sort this one out. Thank you! Narayan

Hi, @Dustin Martin , thanks for piping in! Would you happen to have an example of what you mean? I tried altering @Narayan Raum 's custom prompt code suggestion, but couldn't get it to work. Here's what he said he thought should work but it didn't: queueTopic:parentTopicGroup:name=Strategy&queueTopic:parentTopicGroup:name_Mod=cicontains I tried changing that to this: queueTopic:parentTopicGroupID=Strategy&queueTopic:parentTopicGroupID_Mod=cicontains But I get no results when I use that prompt. If you have any suggestions for how I can try your recommendation I would really appreciate it. Thanks so much! Rani Rani Paul One &All