Can't Delete Resource from Task -- Suspect Actual Thru Date

[Anon Anon]

Hello  I have a resource assigned to several active tasks. (There is another resource assigned to the same tasks as well.) I would like to delete the resource from the task--I have zeroed out ETC and there are no actuals associated with the resource on these tasks. When I click REMOVE box, the system displays a red message "PRJ-07582: One or more assignments cannot be deleted. This may be due to committed assignment actuals." The offending resource has an Actual Thru Date (10-24-09) and the task's Start Date is 6/11/2010 and Finish is 6/17/2010.  I suspect this Actual Thru Date is the culprit but can't seem to change/delete it. It appears for the resource I can't remove. It does not appear in the other resource and I have been able to remove/re-add it. Any suggestions would be appreciated.  Larry

[Anon Anon]

Although this board question is dated, I ran into the same issue trying to delete a task from a WBS which appeared to have no actuals charged against it but issued the same error message.
I found that even though the resource(s) attached to the task in question are showing "0" actuals, they infact are "zero" actuals and not "never submitted time" actuals.
At one point and time the resources in question charged time to the task, and even though they adjusted it after the fact, the 0 value is being treated as a posted actual.
I confirmed this by finding the adjusted timesheet for the resource in question.
It appears that the "Actual Thru Date" presence, or lack thereof, referenced in the origial post is what would indicate if it was an adjusted 0 value actual or if the 0 was in fact a "never submitted time" representation.
Once the resource charges time to the task the "Actual Thru Date" would populate, however, if the resource doesnt post time to the task it remains null.

[Deactivated User]

Thanks for sharing.

Were you able to remove the resource from the task after deleting the Actuals through date?

Martti K.

[Legacy User]

The reason why the resource cannot be removed from the task is that this would delete the assignment, so that a record would be removed from prassignment. This would leave a phantom assignment reference in the timesheet's prtimeentry table. Not good.

 

This is not to say an idea cannot be submitted for a re-design that would handle a scenario like a resource being mistakenly added to a task charging time and you are stuck with this unwanted assignment