To expand on @Rick_MacDuffie's solution, I use this one: displayname=Active Task listdelimiter=<hr> listmethod=nested(tasks).lists styledef.case.0.comparison.icon=false styledef.case.0.comparison.leftmethod=ID styledef.case.0.comparison.lefttext=ID styledef.case.0.comparison.operator=notblank styled...

I think there's some disconnect with the way your tasks and form are set up. If you have the form on EVERY task, then EVERY task will have that field. The text mode code will read THAT field on THAT predecessor task and display it, every time. But only if that field is on every single predecessor ta...

If you're in a task report, you can remove the "task" part of listmethod=nested(task.predecessors).lists so it reads  listmethod=nested(predecessors).lists  That sample is for an Assignment report

You would need to make a Product A field and a Product B field as radio buttons and hide any other choices. The user could then select the relevant one of them and leave the other alone, if you wanted a single form. If you wanted 2 forms, you could preselect Product A on one of them and Product B on...

That could work as well in a different way. I think what OP really wants to see is all tasks (any status, parent or child) under an incomplete parent task. "so only Incomplete parent tasks and their child tasks are visible" @HazelNB is this what you're looking for?

I doubt it but you can set custom forms based on topic. That could solve your problem by having a "Form A" and a "Form B". And you can also set up a form that shows certain fields if the user makes a specific choice on another field if you wanted a single form. TIP: if this solved your problem, I in...

I use the following to display the predecessor and successor with the task number, name, primary assignee, and planned completion date.   displayname=Predecessor(s) listdelimiter=<br> listmethod=nested(task.predecessors).lists textmode=true type=iterate valueexpression=CONCAT("(Task#: ",{predecessor...

Although you could just use:     parent:status=CPL parent:status_Mod=notin     There is one fatal flaw in the entire concept. If, according to best practice, you have the entire task list under a "Summary" task, parent tasks immediately below that will always be displayed as long as ANY task is not ...

Every time I see that lion logo I think it's the Brave browser logo, or the dozens of other companies that use it!

Just an FYI: If you disallow users to create their own views, as is good practice, they will not be able to select columns that you set for them.