Duplicate IDs
In the Open Standard
Tim DaviesMember for 21 years 1 month
- Created
- 11
- 2
0
I have been amending a copy programme to suit a new project, which has some repeated sections of work. The first thing I have done is amend the project WBS, deleting some branches and renumbering others.
The activity numbering has now changed within the project and I now have many activities with different activity names, but the same ID. As many as four, activities have the same ID. Some are sitting within the same WBS section, others in different sections.
How can this happen? What is the best way to sort this out?
The activity numbering has now changed within the project and I now have many activities with different activity names, but the same ID. As many as four, activities have the same ID. Some are sitting within the same WBS section, others in different sections.
How can this happen? What is the best way to sort this out?
11 replies
Oldest first- 0Steven Oliver ·First off, are you sure ?
Could try going to the Enterprise, Projects, Defaults Tab.
Change Activity Id Prefix and Activity Id Suffix values to
annotate new values.
Back to Project,Activity view. Remove all Group and Sort levels. Then do a copy/paste. Your new activities will be annotated with the values you chose earlier. The original values can then be deleted.
HTH
- 0Henk van der Heide ·Tim,
The activity ID has to be unique within your project. But when you copy the project you dont have to change your id’s.
The unique id is created as an combination of the project and the activity id. So when you open two or more projects it looks like you’ve two equal id’s in the project, but this is not possible.
Regards
Henk
- 0Kevin Button ·Duplicate activity IDs within a project was in fact a bug in an earlier version. I found this could happen with copy and paste, and when reporting to Primavera with the exact steps I had taken, they acknowledged it was a bug. I am now using version 4.1 and cannot duplicate IDs within a project.
- 0Tim Davies ·Thanks Kevin,
Its nice to know that someone else has experienced the same type of problem, especially as it is something as fundimental as duplicate IDs. Its so basic to any database that you don’t have duplicates of a key field.
I guess it could make a difference, which database P3e is running on. I am running a standalone, local installation, so guess I can’t trust the interbase installation. Perhaps it would not be a problem with an Oracle or SQL installation?
Thanks for letting us know that the problem is solved in version 4.1. I guess the same would go for version 5.0! - 0Kevin Button ·I have just found that the problem still exists in 4.1. On the Primavera knowledgebase, solution prim15837 says "If a WBS node is copied and pasted within the same project, activities are created with a duplicate Activity ID." It goes on to say that "The problem only occurs when you copy a WBS, then paste it to the same location (without moving the cursor) and if the option to auto-number new activities based on the selected activity is checked."
Hopefully this has been fixed in 5.0
Cheers - 0Shahzad Munawar ·This is generic problem of P3 that during copying and pasting in the same project,you have to alloted other IDS than already placed.
Right so that this duplication of IDS needs to be rectified in new versions.
Not limited to above, previous suggestions such as retrieve the activities after deletion were not considered by P3 Developers so far in any version and same like others functions
so wait when P3 Developers think over this. - 0Henk van der Heide ·Shahzad,
I’m told that the new release of P3e has an undo function.
A negative aspect of undo is that it uses a lot of memory (so im told again). Until now we were forced to make a back-up on regular basis an to be onnest i think it workt very fine. But undo will even be better.
Maybe Primavera has listened a little bid.
Regards
Henk
- 0Marian Anyameluhor ·
Activity IDs: The SDEF
Activity IDs: The SDEF standard does not support activity IDs longer than ten characters, while P6 projects may contain activity IDs longer than ten characters. Activity IDs are truncated to the first ten characters when converting a P6 project to SDEF. Due to this truncation, it is possible that duplicate activity IDs will be encountered during the conversion; if so, the conversion is aborted. To ensure that conversions to SDEF are not aborted, P6 projects should not contain activity IDs longer than ten characters. If activity IDs must be longer than ten characters in P6, the first ten characters must be unique.
http://pmsite.com/forums/viewthread/860/
Hope this helps
Log in or join to reply
ProjectControls.com is free to join. Members can post questions, reply, vote and follow discussions.
Existing members: your original username and password still work. Forgot password?