how do i reset the Unique ID field in Project 2003?

C

Carrie Jensen

I'm using a template given to me and the Unique ID field needs to be reset
for my project.
 
J

Jim Aksel

CTRL+A to select all tasks (Make sure all tasks are visible first)
CTRL+C to copy all tasks
File/New... (or the new file icon)
CTL+V to paste the tasks to a new location

Insert the UniqueID column to verify the Unique ID's have reset.
--
If this post was helpful, please consider rating it.

Jim Aksel, MVP

Check out my blog for more information:
http://www.msprojectblog.com
 
C

Carrie Jensen

Jim - thanks for the suggestion, however I have custom fields, tables,
etc....that would all have to be copied over using the organizer and reset up
in the new plan....as well as the project start date....so that seems to be
the LAST resort I should take.
 
J

Jim Aksel

The UniqueID field is just as a in a database table. It cannot be altered or
re-used once retired.

Perhaps you can explain why you feel the UniqueID "must" be reset and there
may be some other alternatives. Normally the UniqueID is not considered for
most things that are done with a schedule unless you are programming.

So, what is the end goal? You can always re-number the TaskIDs (not the
UniqueIDs) from Project/Sort/Sort By.... and select the "Permanently
renumber" at the bottom fo the window.
--
If this post was helpful, please consider rating it.

Jim Aksel, MVP

Check out my blog for more information:
http://www.msprojectblog.com
 
C

Carrie Jensen

I delete/add tasks and thus the "ID" field would change from version to
version. There is no specific Task ID column that can be renumbered and then
kept constant through you add/remove tasks?
When referring to a task # with another staff member...they are looking at
the WRONG task because it's changed in my version.
I did try what you suggested, but I lost all formatting (colors/fonts) when
pasting to the new project file. This file is over 3000 tasks, so this is
not looking good for me. HELP??
 
J

Jim Aksel

Based on your response, we may have some terms mixed up. Here are the
definitions from "Help." I appoligize in advance if this is information you
already have or know.... just trying to be clear.

TaskID: The number on the very left side of the file. It changes if the
task moves.

UniqueID is different than the TaskID, it never ever changes even if the
task moves. From the help:

As you create new tasks, Project adds a unique number to each task in the
project. This number is unique in that it is never rearranged or reused if
the task is moved or deleted.

If tasks are moved, inserted, or deleted, the task IDs change to reflect
the new task sequence. However, the Unique ID always remains constant,
regardless of any editing.

Might I suggest to use the *UniqueID* as it is. Insert the column UniqueID.
In this case, TaskID 22 may be UniqueID 2345 but that 2345 will be the same
in ALL files that originated from the same ancestor. It may be TaskID 27 in
the PM's copy but it will still be UniqueID 2345. So, the file you e-mailed
to the PM will still have the same UniqueID for task name "Approve Spec" as
in your file... even if you have added or deleted tasks.

There is one schedule habit you need to adopt. Do not cut/paste tasks and
do no delete the task and retype it elsewhere as this does change the
UniqueID. Instead, use drag/drop.

Also, keep only one copy of the schedule as the official version... you
don't want the remote PM to make changes (add/delete tasks) and then use his
copy. You want to adopt a "sacred" master copy that only you as the master
scheduler will use for all official documents, etc.
--
If this post was helpful, please consider rating it.

Jim Aksel, MVP

Check out my blog for more information:
http://www.msprojectblog.com
 
R

Rod Gill

Make a habit of only moving tasks by clicking and dragging them. Cut and
paste does create a new Unique ID

--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA, see:
http://www.projectvbabook.com




Jim Aksel said:
Based on your response, we may have some terms mixed up. Here are the
definitions from "Help." I appoligize in advance if this is information
you
already have or know.... just trying to be clear.

TaskID: The number on the very left side of the file. It changes if the
task moves.

UniqueID is different than the TaskID, it never ever changes even if the
task moves. From the help:

As you create new tasks, Project adds a unique number to each task in the
project. This number is unique in that it is never rearranged or reused if
the task is moved or deleted.

If tasks are moved, inserted, or deleted, the task IDs change to reflect
the new task sequence. However, the Unique ID always remains constant,
regardless of any editing.

Might I suggest to use the *UniqueID* as it is. Insert the column
UniqueID.
In this case, TaskID 22 may be UniqueID 2345 but that 2345 will be the
same
in ALL files that originated from the same ancestor. It may be TaskID 27
in
the PM's copy but it will still be UniqueID 2345. So, the file you
e-mailed
to the PM will still have the same UniqueID for task name "Approve Spec"
as
in your file... even if you have added or deleted tasks.

There is one schedule habit you need to adopt. Do not cut/paste tasks and
do no delete the task and retype it elsewhere as this does change the
UniqueID. Instead, use drag/drop.

Also, keep only one copy of the schedule as the official version... you
don't want the remote PM to make changes (add/delete tasks) and then use
his
copy. You want to adopt a "sacred" master copy that only you as the
master
scheduler will use for all official documents, etc.
--
If this post was helpful, please consider rating it.

Jim Aksel, MVP

Check out my blog for more information:
http://www.msprojectblog.com





__________ Information from ESET Smart Security, version of virus
signature database 4559 (20091030) __________

The message was checked by ESET Smart Security.

http://www.eset.com

__________ Information from ESET Smart Security, version of virus signature database 4559 (20091030) __________

The message was checked by ESET Smart Security.

http://www.eset.com
 
R

Rick B.

Cutting and pasting causes all kinds of problems. The simple need, when
starting a new project file from another is to reset the Unique IDs and then
baseline the file everywhichway. Any seasoned PM would know the value of
this. This should be the default option when a new MPP is saved from a
template.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top