A
anovak
I had a recent post concerning this situation where you add a resource
to a task, the resource submits actual work against that task, then
when you add another resource to the task, you get a corrupted
assignment which apparently can be fixed by running a query to
identify the subject assignments, and then setting the respective
"Publish" flags to "No", republishing, then changing the values again
to "Yes" and republishing again. Whew!
OK..it appears that through all this several of the team members have
lost data they had input for a month. Does this mean that anything
they have entered that has not been submitted and accepted will be
overridden by the blank values in the Project (pre-task acceptance)?
Sounds to me like its a no-win deal. They can't get to the My Tasks
page and the only way to fix it results in blowing away the data
they've entered.
Any best practices that should be followed here other than making darn
sure that they submit at least each week (probably safer to submit
each day) and ensure that the PM has accepted the changes? I'd say
that business rule for auto accepting would come in handy here.
Any and all comments, suggestions, warnings, etc. would be
appreciated.
Is there a HotFix out there for this or any known schedule for SP2
that might include this fix?
Best,
Andy Novak
UNT
to a task, the resource submits actual work against that task, then
when you add another resource to the task, you get a corrupted
assignment which apparently can be fixed by running a query to
identify the subject assignments, and then setting the respective
"Publish" flags to "No", republishing, then changing the values again
to "Yes" and republishing again. Whew!
OK..it appears that through all this several of the team members have
lost data they had input for a month. Does this mean that anything
they have entered that has not been submitted and accepted will be
overridden by the blank values in the Project (pre-task acceptance)?
Sounds to me like its a no-win deal. They can't get to the My Tasks
page and the only way to fix it results in blowing away the data
they've entered.
Any best practices that should be followed here other than making darn
sure that they submit at least each week (probably safer to submit
each day) and ensure that the PM has accepted the changes? I'd say
that business rule for auto accepting would come in handy here.
Any and all comments, suggestions, warnings, etc. would be
appreciated.
Is there a HotFix out there for this or any known schedule for SP2
that might include this fix?
Best,
Andy Novak
UNT