C
Chico
When using local resources in Microsoft Project Server
2002 ... what is the reason when deleting a delete local
resource from a project plan that BOTH THE RES_UID and
RES_ID are resequenced on the MSP_PROJECTS table. Am I
missing something? This seems to be a glitch in the
software. The RES_ID is a sequence number for the
plan ... so it should be re-sequenced. However, the
RES_UID for the plan should.
If the data is exported from Microsoft Project to a third
party application, there is no way to no what was deleted.
For example, you have local resources Al, Betty, and Carl
(with respective RES_UID and RES_ID of 1, 2, and 3).
Betty gets deleted from the project plan in project server
2002. Project software updates the resource ids as
follows: Al (RES_UID = 1, RES_ID = 1), Carl (RES_UID = 2,
RES_ID = 2) ... shouldn't Carl be updated to (RES_UID =
3 ... i.e. stay the same, RES_ID = 2).
The problem with the way it works now is the creating some
custom tables to link the local plan resources with a
third party application (i.e. to link the "unique" local
plan id ... which would be combination of project id and
RES_UID ... to an id known in the third party
application) ... you don't know which resource was
deleted. You can't tell by the name because that could
have changed as well.
The way it works now ... what is the purpose of the
RES_UID? It is just cloning what the RES_ID (which is a
sequence number) is doing.
In summary, the way it works now means when project server
deletes a local resources (or for that matter deletes one
and adds one) in Project Server 2002, there is no way to
sync up with a third party application ... since the name
can also change ... and the custom field in microsoft
cannot be used being than cannot be protected from
updating when using project.
Make sense? A bug that should be fixed? Some other way
around it? Thanks!
2002 ... what is the reason when deleting a delete local
resource from a project plan that BOTH THE RES_UID and
RES_ID are resequenced on the MSP_PROJECTS table. Am I
missing something? This seems to be a glitch in the
software. The RES_ID is a sequence number for the
plan ... so it should be re-sequenced. However, the
RES_UID for the plan should.
If the data is exported from Microsoft Project to a third
party application, there is no way to no what was deleted.
For example, you have local resources Al, Betty, and Carl
(with respective RES_UID and RES_ID of 1, 2, and 3).
Betty gets deleted from the project plan in project server
2002. Project software updates the resource ids as
follows: Al (RES_UID = 1, RES_ID = 1), Carl (RES_UID = 2,
RES_ID = 2) ... shouldn't Carl be updated to (RES_UID =
3 ... i.e. stay the same, RES_ID = 2).
The problem with the way it works now is the creating some
custom tables to link the local plan resources with a
third party application (i.e. to link the "unique" local
plan id ... which would be combination of project id and
RES_UID ... to an id known in the third party
application) ... you don't know which resource was
deleted. You can't tell by the name because that could
have changed as well.
The way it works now ... what is the purpose of the
RES_UID? It is just cloning what the RES_ID (which is a
sequence number) is doing.
In summary, the way it works now means when project server
deletes a local resources (or for that matter deletes one
and adds one) in Project Server 2002, there is no way to
sync up with a third party application ... since the name
can also change ... and the custom field in microsoft
cannot be used being than cannot be protected from
updating when using project.
Make sense? A bug that should be fixed? Some other way
around it? Thanks!