Hello, I wouldn't mind the invite if there's room for 1 more! Please let me know what information you'd need. Thanks,Ryan

I'm not sure of that answer to that one, I suspect it's a no on a custom form but you could probably get that on a report if task 1 is a predecessor of task 2. Then build the task level report around task 2 while displaying predecessor details as columns as well. Another idea is you could build a Pr...

We have the Project Brief positioned at the Program level on a custom form as well. When building Project level reports, I link out to that tab specifically with a URL instead of displaying that information on the report itself. It's not perfect, but that more detailed information is just a click aw...

On your Task level custom form, add a calculated field and your calculation should just be Project.YOUR FIELD NAME to pull information down from your Project level to the Task level. You can do the same for Program to Project too. Don't forget to click that Update in Background button as you're me...

I tried that too and wasn't having much luck there either, but I personally haven't used Milestones a great deal. My workaround thus far has been to use a Task report to "fake" a Project report and that seems to be OK. I've pushed program+project level information down into a task level custom form...

Thanks, I appreciate the reply! I have that part working in some other reports, probably after coming to the WF community here! The problem is that I can't sort or filter if I reference the task collection on a project level report - I can only display it and that's all. Is it possible to write th...

Our organization has a specific task that ends up being more critical than the actual closure of the overall project. I'd like to bring the projected completion date of that task "up" to a project level custom form so I can use it easier on reports - for filtering, sorting, grouping, etc. I'd think ...

So clever, yes that totally worked. Thank you so much, this has been bugging me for too long now. Will have to remember that trick for other scenarios, thanks again!

Thanks for taking a look, I really appreciate it. I was hoping to avoid that one, just to avoid cluttering up the custom forms more, but that does work for the report side so might be the way I go. Thanks again!

Hi Sarah, Nothing specifically I'm doing. The first Doc ID and Title column is just the default Project Name field, no text mode updates. At any rate, here's that column if there's something I should change in there. Otherwise, everything else is basic plain text. descriptionkey=namedisplayname=D...