A
abisabado
Hello,
Has anyone experienced this scenario.
A custom enterprise duration field was created to store a value
manually. (Enterprise Project Duration Field 1)
It was observed by one of our PM's that this value changes every time
the timesheet is approved. I didn't think so because I know Project
Server database and I know that these values from the timesheet
updates are stored in a separate table and there was no way this could
affect the duration field.
However, one time when I updated my project plan, I noticed that the
project duration field in question was actually changed without me
doing anything and I checked it was last saved by me, and the last
action I did was to approve timesheet updates.
Example:
Before timesheet approval: Enterprise Duration Value = 52
After timesheet approval: Enterprise Duration Value = 4.21
Why does this happen? How does Project Server store duration entered
in a custom enterprise field? There shouldn't be any calculation
because this is manually encoded and should not change at all.
Any idea why this happens?
Has anyone experienced this scenario.
A custom enterprise duration field was created to store a value
manually. (Enterprise Project Duration Field 1)
It was observed by one of our PM's that this value changes every time
the timesheet is approved. I didn't think so because I know Project
Server database and I know that these values from the timesheet
updates are stored in a separate table and there was no way this could
affect the duration field.
However, one time when I updated my project plan, I noticed that the
project duration field in question was actually changed without me
doing anything and I checked it was last saved by me, and the last
action I did was to approve timesheet updates.
Example:
Before timesheet approval: Enterprise Duration Value = 52
After timesheet approval: Enterprise Duration Value = 4.21
Why does this happen? How does Project Server store duration entered
in a custom enterprise field? There shouldn't be any calculation
because this is manually encoded and should not change at all.
Any idea why this happens?