{"id":7633,"date":"2014-10-12t04:00:44","date_gmt":"2014-10-12t08:00:44","guid":{"rendered":"\/\/www.deco-dalles.com\/?p=7633"},"modified":"2019-10-09t13:20:58","modified_gmt":"2019-10-09t17:20:58","slug":"foiled-excel-import-primavera-p6","status":"publish","type":"post","link":"\/\/www.deco-dalles.com\/foiled-excel-import-primavera-p6\/","title":{"rendered":"the one indicator that can foil your excel import into primavera p6"},"content":{"rendered":"

there is the temptation to think that because you can export a data field from primavera p6<\/a> to excel that you can import the same data field back to primavera p6 after manipulating the field\u2019s data in excel.<\/p>\n

if you have ever imported data into primavera p6 using excel, you would have experienced instances where despite getting the familiar message of a successful import, some of the changes you made in excel were not reflected in primavera p6.<\/p>\n

the reason for this is that primavera p6 uses a relational database (e.g. oracle xe or sql server express) to store data. in relational databases, not all data you see displayed are stored in the database, some are calculated and these calculated fields cannot be imported into the database.<\/p>\n

so to help planners and schedulers identify fields that cannot be imported, primavera p6 attaches the prefix \u201c(*)<\/strong>\u201d before the title of these fields in the excel import file.<\/p>\n

\"foil-excel\"from the screen shot above, the following fields cannot be imported into primavera p6:<\/p>\n