L
LT
I've noticed that Assignment.TaskUniqueID bahaves differently depending on
whether the code is running in an MPP file of in a check-out Project Server
project.
In an MPP file, Assignment.TaskUniqueID works as advertised. I can find the
corresponding Task.UniqueID for each Assignment.TaskUniqueID.
However, in a check-out Project Server project, when I retrieved the
Assignment.TaskUniqueID, I can NOT find the corresponding Task.UniqueID.
What's interesting is that most of the Task.UniqueID's are 4-digit numbers
such as 7056, but most of the Assignment.TaskUniqueID's are 7-digit numbers
such as 8395702.
Does anyone knows why Project is behaving this way?
whether the code is running in an MPP file of in a check-out Project Server
project.
In an MPP file, Assignment.TaskUniqueID works as advertised. I can find the
corresponding Task.UniqueID for each Assignment.TaskUniqueID.
However, in a check-out Project Server project, when I retrieved the
Assignment.TaskUniqueID, I can NOT find the corresponding Task.UniqueID.
What's interesting is that most of the Task.UniqueID's are 4-digit numbers
such as 7056, but most of the Assignment.TaskUniqueID's are 7-digit numbers
such as 8395702.
Does anyone knows why Project is behaving this way?