We've done such copy from parent to child processes several times - and when they fail, they cause nothing but headaches. If only I could start over...
Still, customers want to see the parent info when looking at the child in list views, and they want to be able to edit in the list view - who would not want this? Problem is that the two out of the box methods (object base list, NSQL based list) don't meet all requirements (Object based list won't provide parent content, but can edit; NSQL based list can read from parent, but can't edit).
Ugh!!!
What to do?
Build an editable HTML portlet - XOG the contents out using WSDL/Soap call, edit, save back - or use the Restful APIs coming in newer versions.
Kevin Mah posted this in another thread: CA PPM 14.x: Integration Using WSDL 300 (33CLR3023S)
Under "What you will learn" it states: Work with WSDL objects, so you can work with CA PPM objects to perform
read/write actions.
Result should be best of all
- ability to read parent content when displaying children in list views
- ability to edit/save changes to children
- no processes copying data back and forth and no data errors when these processes fail
Using this method, if project has more than one parent, could then include the Allocation% for each so that users can see how their projects roll-up to their parents. We do this in one of our reports, not yet via HTML portlet.