Hi @SteveOw, It's possible to solve your requirement without going into textmode: the trick is to set up multiple Advanced Formatting rules in "top down" order. In your case, for example, you could: return to the visual (non-text) mode of the Advanced Settingsedit your first rule to instead "not do...

 Hi @Himanshu4, There is no native way to copy custom data between objects that are peers (e.g. Projects, in your case), so instead you might consider: storing the data at a higher level common to each project (e.g. Program, Portfolio, Company), assuming it is the same for ALL projects to then refer...

 Hi @Holly_Benjamin, Getting accurate burn calculations at the Portfolio and Program level is beyond Workfront's native reporting capability, so I invite you to consider our AFA Burn List, Budget vs Actual Quarterly Burn, and/or Budget vs Actual solutions, then email me at doug.denhoed@atappstore.co...

My pleasure Eric, A Journal Entry report would return one row per Update (using ORs and cicontains, similar to the above)…but I suspect that pulling in the Project milestone info from there might be too many hops (untested). If you get stuck, I invite you to consider our Magic Reports solution, whic...

Hi @Eric_D_Miller, While it might be possible to create such a Notes report, given the work you’ve already accomplished on the Project report, and assuming that one row per project (vs one row per keyword occurrence across what could be multiple notes) is preferable, I’d suggest you stick with the l...

 Hi @MelanieM1, I can offer a couple of suggestions for inspiration and/or installation: Our UserWatch solution equips you with a set of informative Workfront based reports on a centralized dashboard which you can use to monitor usage and encourage adoption in an easy, transparent, and fun manner; a...

 Hi @Ryan_McGee, Ehm...yes (to spare you)... Using a Project report in this manner is likely insane, in my opinion. To achieve a similar grid output, I'd instead suggest a Task report in matrix mode with one row per project, one column per task, and the information as you've proposed as the cell val...

 Hi folks, Shout out to @skyehansen... I had made note of your Approval Status Collection filtering technique when you first raised it, and returned to it today to DRASTICALLY simplify some project report approval filtering for one of my other SysAdmin colleagues. Instead of checking for certain Ap...

 Hi @AdrianneCole, In addition to the Journal Entry based approach @skyehansen  mentioned, I invite you to also: avoid our Project Management Time Travel approach (which was ill conceived)learn about our Automatic Weekly Status Reporting technique (which is sound)consider our Executive Status Report...

 Hi @MeshackOm1,I invite you to consider our Capacity Charts solution, which allows you to easily create insightful resource management reports with only basic Workfront setup. I'd be happy to chat further via doug.denhoed@atappstore.com Regards,Doug