Forum Discussion
JuanSolorio1
12 years agoQrew Cadet
Thank you for offering this solution.
However, there's one huge issue with it and we only discovered it after implementation. While the solution works well for successors and for the immediate predecessor to the currently open task , the "End Date for Predecessor" formula causes ALL completed predecessor tasks to update their Projected Finish Date as well, so the original functionality requested is not met which was to KEEP the original Projected Finish Date of the preceding taskS intact to be able to see if those tasks finished early or late.
The ideal scenario would be to be able to lock the Projected Finish Dates of COMPLETED predecessors so that we could determine whether they were completed early or late, and to only update the Start Date of incomplete successors using the "End Date for Predecessor" formula as outlined above (Projected Finish Date if predecessor is open, or the Actual Finish Date if predecessor is complete).
Can this be done?
Thanks in advance.
Juan
However, there's one huge issue with it and we only discovered it after implementation. While the solution works well for successors and for the immediate predecessor to the currently open task , the "End Date for Predecessor" formula causes ALL completed predecessor tasks to update their Projected Finish Date as well, so the original functionality requested is not met which was to KEEP the original Projected Finish Date of the preceding taskS intact to be able to see if those tasks finished early or late.
The ideal scenario would be to be able to lock the Projected Finish Dates of COMPLETED predecessors so that we could determine whether they were completed early or late, and to only update the Start Date of incomplete successors using the "End Date for Predecessor" formula as outlined above (Projected Finish Date if predecessor is open, or the Actual Finish Date if predecessor is complete).
Can this be done?
Thanks in advance.
Juan