Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

WBS Names not updating during import to P6

3 replies [Last post]
Ian Wilkinson
User offline. Last seen 8 years 34 weeks ago. Offline
Joined: 20 May 2005
Posts: 6
Groups: None

I have an existing project in my portfolio which I recieved from a contractor. I received an update of the project from the contractor and imported the update into my existing project using the option "Update Existing Project". The WBS option was set to "Update Existing". I imported the project. I then checked the updated programme with a PDF supplied by the contractor and found that the WBS Name had not changed in the updated programme compared with the WBS name on the PDF. I phoned the contactor who confirmed the WBS name on his project agrees with the PDF. Somehow, the WBS has failed to update during the import/update existing programme.

Any Ideas?


Zoltan Palffy
User offline. Last seen 8 hours 45 min ago. Offline
Joined: 13 Jul 2009
Posts: 2531
Groups: None

try insert new for the wbs

Binu Thankaian
User offline. Last seen 52 weeks 17 hours ago. Offline
Joined: 6 Aug 2015
Posts: 3
Groups: None

While doing update transfer in the same programme with different update, after impoting into the programme, the WBS not found in the programme. but the Import was successful. 

Rodel Marasigan
User offline. Last seen 33 weeks 5 days ago. Offline
Joined: 25 Oct 2006
Posts: 1516

I also experience the same before and when I done my investigation why it was happening I found out that if you used import to update the existing projects it will not touch or delete Activity ID but can add if not exist, update WBS if the activity is already assigned to existing WBS and many others. The reason why is because these are the basic unique identifier of an existing project on Primavera database. During my analysis, I tried a force update using direct modification on Primavera database table and lost other connections to related tables like PROJWBS, TASKRSRC, ROLES, RSRC, ACCOUNTS..etc. It will import everything if you select create a new project instead of update existing.

Note: XER will not modified existing records on TASK table for Activity ID, Resource assignment, Resource, WBS and will add instead if these are change from the original Projects. Sometimes it may not also update relationship, cost account and roles to existing activities. You can check all fields that not updatable using the excel export. Any fields with * is not updatable.