Project for the Web Scheduling Engine Bug
Error Description There appears to be a bug in the Project for the Web scheduling engine where Effort, Effort Completed, Effort Remaining, and % Complete do not stay in sync. This appears to depend on the sequence in which they are modified. GIF below showing a live example: Testing & Reproduction Of Error I devised a test to determine in which cases this behavior occurs: I created 24 tasks in a Project I modified values for each of them in different orders (they all were given a starting Effort of 10h and the project is set to Fixed Effort). Each task was modified 4 times - once for each of: Effort, Effort Remaining, Effort Completed, % Complete I made these modifications in every ordered permutation of those 4 values (hence the 24 tasks) I labeled which ones "failed" (their values got out of sync) and which ones "passed" I also took note of which step they got out of sync at I stopped at the "failing step" each time and did not make additional modifications (see note on this later in post) Test Results NOTES: Tasks in the data below are named according to the edit sequence. EF=Effort, ER=Effort Remaining, EC=Effort Completed, %C=% Complete Screenshots below are from my Org's default environment but I have reproduced this in a CDS/Dataverse named environment (configured for vanilla P4TW) Assigning (or not assigning) resources to the tasks appears to have no impact on this behavior Final Project State with Pass/Fail labels Here's the final state of the Project after all edits: Where Did We Go Wrong? The below table documents where in the sequence each task's data got out of sync. You'll notice that most of them did get out of sync (this is really not good), but a few stayed in sync: NOTE: Examples are not presented here, but continuing to change values after the data gets "out of sync" does not eventually result in the data getting back in sync. It appears to permanently remain out of sync once it's gotten into this state. The only resolution that I have found is to delete the task and re-start. Apparent Cause After boiling down the above information, it appears that this issue occurs when modifying values in the following sequences: % Complete -> Effort % Complete -> Effort Remaining Effort Completed -> Effort Effort Completed -> Effort Remaining Put more concisely, this seems to be caused by the following sequence: { % Complete | Effort Completed } -> { Effort | Effort Remaining }
