I've always done it by opening the filter and deleting the conditions and the name of the filter. Then click "OK". Not sure if there's a better or faster way, but I know that will work.

I don't think there's anything wrong with the formulas themselves. I'm seeing the same results in my environment. I think it has more to do with the timezones in Workfront. I did a similar report and added columns for "Start" and "End" dates, setting valueformat to display longAtDate (here's the co...

Hi Nick! Try to change "group.1.valueformat=customDataLabelsAsString" to "group.1.valueformat=HTML" and see if that does the trick for you. It returned results in my environment, so I'm hoping you'd have the same luck.

We have users in our system who provide a drop report to our call center, so they know the jobs that are being deployed to customers each day, as well as the counts for the drop. We have email components, as well as direct mail components, so there's a date field on each project for Email Drop and D...

Hi Kundan! The outputs for DSC11 & DSC12 are strings, not integers. So if you wanted to extract a number from those fields, are you just wanting to capture the first number in the selection? So if someone selects "5 - For value more than...", you'd want the sum to capture the value "5" and then add ...

One (confusing) thing worth mentioning is that WEEKDAYDIFF and DATEDIFF have inverse syntax - so in WEEKDAYDIFF, Date 2 variable is listed first, but in DATEDIFF formula, Date 1 is listed first. You can see a list of formulas and their syntax here. In your example, I set Approval Start Date as the "...

Hi Dan! You have 2 options. If you just want to see the column with the number on a task report, you can set up a column with the following formula: ------------displayname=Weekday Difftextmode=truevalueexpression=WEEKDAYDIFF({approvalStartDate},{project}.{plannedCompletionDate})valueformat=HTML----...

Hi Sandy! The codes can differ depending on the type of report you're using. I've cleaned up the code to only 4 lines in all of these examples. In the task report, we have to specify that we're jumping a level to see the project owner (tasks don't have owners - only primary assignees). The task repo...

Yes, it's possible. This would be the code for a task report: ----------- valueexpression=CONCAT(LEFT({project}.{description},100),"...")valueformat=HTMLdisplayname=Project Description ----------- You can omit the CONCAT() portion if you choose, so it would just be valueexpression=LEFT({description}...

Just had to revise the code in my post because I realized that the EXISTS code needed to have all 3 of the task names listed in each criteria set. And even still, I'm not totally confident that it's going to translate correctly. It seemed to be pulling the right tasks in our environment but I'm not ...