J
JBG
Hi All
I really hope someone out there can help me with the question.
In our Project server 2007 system I have added a custom field on task level.
In every project we add information regarding each task in this field. The
reason for this is to calculate the amount of hours, captured via project
server timesheets, for each of these custom task items.
Week 1 we captured hours and the query that calculates the hours worked
fine. The query running against the reporting database is as follows:
Select <data>
from <timesheet tables>, <task_userview>
joined by taskuid
Week 2 the hours was captured and the report did not pick up the hours.
We then investigated the data and in the timesheettask table the new records
have got a different taskuid than the records of the previous week. We then
opened the project plan with MS project professional and viewed the GUID in
the plan (by making the GUID column visible). The GUID corresponded with the
taskuid in the timesheettask table of the timesheets entered in week 1. We
also ran a trace to see which stored procedures etc. is being executed. In
one stored procedure we noticed that the task_saved table is being used. We
then queried (on the published database) the assignments and
assignments_saved tables and noticed that the assignments table contain the
GUID as per the project plan and that the assignment_saved table contained
the incorrect GUID, those stored in the timesheettask table for week 2.
This whole story is now resulting in a situation that some taskrecords
cannot be linked to the correct task in the task table, and thus the link to
our custom field is broken. The hours being reported is thus incorrect.
It might sound a bit confusing, but I really need to determine what is
happening.
I really hope someone out there can help me with the question.
In our Project server 2007 system I have added a custom field on task level.
In every project we add information regarding each task in this field. The
reason for this is to calculate the amount of hours, captured via project
server timesheets, for each of these custom task items.
Week 1 we captured hours and the query that calculates the hours worked
fine. The query running against the reporting database is as follows:
Select <data>
from <timesheet tables>, <task_userview>
joined by taskuid
Week 2 the hours was captured and the report did not pick up the hours.
We then investigated the data and in the timesheettask table the new records
have got a different taskuid than the records of the previous week. We then
opened the project plan with MS project professional and viewed the GUID in
the plan (by making the GUID column visible). The GUID corresponded with the
taskuid in the timesheettask table of the timesheets entered in week 1. We
also ran a trace to see which stored procedures etc. is being executed. In
one stored procedure we noticed that the task_saved table is being used. We
then queried (on the published database) the assignments and
assignments_saved tables and noticed that the assignments table contain the
GUID as per the project plan and that the assignment_saved table contained
the incorrect GUID, those stored in the timesheettask table for week 2.
This whole story is now resulting in a situation that some taskrecords
cannot be linked to the correct task in the task table, and thus the link to
our custom field is broken. The hours being reported is thus incorrect.
It might sound a bit confusing, but I really need to determine what is
happening.