19-11-2021
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Thought I’d add this, in case anyone else finds it helpful. Hopefully it makes sense.
We had an immediate need for establishing a parent/child relationship, so we developed sudo relationship using calculated fields and Fusion.
Currently we are using a process where we assign a parent project to each child, using a type ahead field on a custom form on each child project.
Fusion will append the parent project number (We have Fusion generating custom sequential project numbers. For test project it does TESTXXXXXX) and project name to the Child project name. Using a view and grouping then shows us that relationship at the project level.
It’s pretty basic, but gives us an extra level to capture data.
The next phase is getting child info to populate to the parent. In this case we have a custom form on each task of the parent project, and we again use a type ahead, this time assigning the child project to tasks on the parent.
This custom form then pulls basic info from the child project to the associated task on the parent project (Calculated fields populate with Child Project ID, Child Project Status, Child Project Percent and child start and end dates).
From here we have Fusion update the Parent task percentage and dates with whatever the child task percentage is and dates are, giving the following results:
We’re still testing the child rollup to the parent, and the biggest issue so far is that the calculated fields need to be “kicked” to recalculate.