Hi Matthew,  I too would like to hear how other customers have come up with work arounds for sublists as there are a couple ways of doing it.  Currently our product does not support dynamically created sub-lists of any sort - this would be a great feature enhancment that we have wanted for a short time now (getting multiselect lists and scoring on pick lists was the first main enhancment we wanted, and received).  One other enhancement I've wanted is just a dynamically updated list of projects, similar to our Members list function.  This would be ideal over the related items option below.

 I think you can already tell what would be needed but I'll state it out for others:

Yes = Relate the pilot project/item to the new implementation project via related items.  A project view filtering on yes and displaying related items would be valuable in this case.

 No = you would also have a text field called "If No, then reason" and is always present in the fields area but is blank or manually input.  It accomplishes the same means but isn't as clean as a pop up sub field.

Thanks Steve,

For now it looks like we're just going to have to improvise.

I've set up two custom fields. One is called 'Pilot converted to Rollout?' and has a selectable list of states; 1)Yes, 2) No and 3) If No, note why in xyz field. The second CF is status field, I called 'Pilot conversion explanation (if not converted)'. This is a pick list with likely reasons that a pilot may not have converted to a sale.

I think its clear that having the type of functionality you describe above available would be a great benefit in linking 'dependent' projects.

Regards,

Matthew