S
Stephan Steiner
Hi
When doing that in project client, project client automatically recalculates
the other values. I found that if I were to bypass the client and write
directly into the database in PS2003, I could reliably corrupt tasks even
when I recalculated the other values manually (and properly).
I'm wondering how PSI handles this.. suppose you have a task and you change
TASK_REM_WORK in the ProjectDataSet.TaskRow and submit the update.. will the
scheduling engine recalculate the other two values appropriately (I'm
assuming TASK_WORK wouldn't change automatically in the dataset)?
And what about the relationship between Work, Actual Work and Remaining
Work.. I found that I could modify remaining work in the MSP_WEB_ASSIGNMENTS
table in PS 2003 and when adding the appropriate entry to
MSP_WEB_TRANSACTIONS, things would work out after approval of the change.
However, if I also modified Work (basically trying to close down a task by
setting remaining work to 0 and adjusting work appropriately without going
through the timesheet).
Suppose, and I realize it's not the same thing, I'd change both
TASK_REM_WORK and TASK_REM_WORK in a TaskRow and submit the update.. can the
scheduling engine cope with that or will it crash and burn? There are many
other values which trigger an immediate adjustmen in the client.. so
generally I'm wondering how safe it is to modify any entries in a TaskRow or
AssignmentRow which depend on other values.
Regards
Stephan
When doing that in project client, project client automatically recalculates
the other values. I found that if I were to bypass the client and write
directly into the database in PS2003, I could reliably corrupt tasks even
when I recalculated the other values manually (and properly).
I'm wondering how PSI handles this.. suppose you have a task and you change
TASK_REM_WORK in the ProjectDataSet.TaskRow and submit the update.. will the
scheduling engine recalculate the other two values appropriately (I'm
assuming TASK_WORK wouldn't change automatically in the dataset)?
And what about the relationship between Work, Actual Work and Remaining
Work.. I found that I could modify remaining work in the MSP_WEB_ASSIGNMENTS
table in PS 2003 and when adding the appropriate entry to
MSP_WEB_TRANSACTIONS, things would work out after approval of the change.
However, if I also modified Work (basically trying to close down a task by
setting remaining work to 0 and adjusting work appropriately without going
through the timesheet).
Suppose, and I realize it's not the same thing, I'd change both
TASK_REM_WORK and TASK_REM_WORK in a TaskRow and submit the update.. can the
scheduling engine cope with that or will it crash and burn? There are many
other values which trigger an immediate adjustmen in the client.. so
generally I'm wondering how safe it is to modify any entries in a TaskRow or
AssignmentRow which depend on other values.
Regards
Stephan