{"id":38475,"date":"2017-04-29t08:57:34","date_gmt":"2017-04-29t12:57:34","guid":{"rendered":"\/\/www.deco-dalles.com\/?p=38475"},"modified":"2020-09-25t13:14:05","modified_gmt":"2020-09-25t17:14:05","slug":"preview-primavera-p6-xer-file-global-data","status":"publish","type":"post","link":"\/\/www.deco-dalles.com\/preview-primavera-p6-xer-file-global-data\/","title":{"rendered":"how to preview a primavera p6 xer file’s global data"},"content":{"rendered":"

this post is part 2 of our scheduler’s guide to primavera p6 global data and project data. if you have’t read part 1 yet, go have a read<\/a>. in this post, i’ll show you how to preview global data coming from a primavera p6 xer file.<\/p>\n

the concept of global and project data in primavera p6 is important to understand; not so much from a planning & cpm scheduling<\/a> perspective, but from the view of wanting to be able to pass a complete record of a project (or perhaps just the essentials) back and forth between users or databases.<\/p>\n

<\/h3>\n

exporting global and project data<\/h3>\n

when you export<\/a> a project from a database to a primavera p6 xer file (or xml file), all of the linked global objects and the embedded project data are exported along with the project. this makes perfect sense since we need a complete record of the project, all global bits are included.<\/p>\n

on export, there’s no picking what\u00a0goes into the output file. primavera p6 professional just does its thing and exports the project from the database to a file to give you a complete record.<\/p>\n

i suggest that it would be nice to be able to choose to exclude information during the export process<\/a>. wouldn’t it be nice to be able to leave out say cost information, or maybe your personal activity codes, or maybe your notebooks even. but we don’t have a feature like this yet. one way around this is to make a copy of your project and use the copy options to pick and choose what pieces to include in the copy. then you export the copy. we’ve written quite a few articles around importing and exporting<\/a>\u00a0primavera\u00a0p6 xer files to help you.<\/p>\n

 <\/p>\n

global data can be a pain in the #@%ss!<\/h3>\n

ask any multi-national engineering firm and they will tell that the importing of primavera p6 projects into their central p6 database is under strict control by an administrator.<\/p>\n

why is that?<\/p>\n

because any global data in imported primavera p6 xer files pollutes<\/em> their database.<\/p>\n

when you import a project from an xer file, the project data is added to the database (the embedded data). but at the same time, any linked global data in the file, gets inserted into existing global data in the receiving\u00a0database.<\/p>\n

for example, import a project via a primavera p6 xer file and 2 new global calendars are inserted into your enterprise global calendar list.<\/p>\n

\"importing<\/p>\n

 <\/p>\n

and at the same time, global activity codes are inserted into the enterprise list, and cost accounts, and user defined fields, and 世界杯时间比赛时间 , and resource codes, and so on and so forth. this unbridled and uncontrolled insertion of global objects during every import ends up creating a major mess. this mess of unwanted data pollutes a clean and organized p6 database. that’s why p6 administrators can be so grumpy!<\/p>\n

\"importing<\/p>\n

 <\/p>\n

i’ve previously written about how clean up this database mess<\/a> of global data. but preventing it in the first place begins with understanding why it is happening.<\/p>\n

previewing an xer files’s global data before importing<\/h2>\n

so it comes down to control during p6’s import process. this is the moment when you can pick and choose what to bring into your database. but it’s not that easy it is?<\/p>\n

how can you pick and choose what you can’t see?<\/p>\n

we have no facility to preview what global data lurks inside that .xer file we were just emailed. maybe it’s nothing. maybe it’s laden with unwanted calendars and 世界杯时间比赛时间 .<\/p>\n

this where a tool like primaverareader, now schedulereader can help you do a quick audit of an .xer file. in case you don’t know, schedulereader<\/a> is a simple primavera p6 xer file viewer. it allows you to open and view .xer files through an interface that looks and feels just like primavera p6 professional. you can’t edit any data in the xer file, but you can view it and do a quick audit to what global data is included.<\/p>\n

\"primaverareader;<\/p>\n

to audit what global calendars are included in your inbound xer file, you could use the calendars button in schedulereader. the calendars screen in schedulereader provides you with a list of all global and project calendars used in the project. from here, you can tell what global calendars will be imported into your database.\"schedulereader<\/p>\n

you can also see other linked global data like 世界杯时间比赛时间 , or global activity codes. for global activity codes, you can pull open the column chooser window (activity table button) in schedulereader. if you see columns listed under the header “activity codes – global,” then you know they exist. you’ll see a similar list of project activity codes columns if they exist.<\/p>\n

\"schedulereader<\/p>\n

schedulereader can also show you other global data including 世界杯时间比赛时间 , roles, resource codes, project codes, udfs and probably some others. all the data will be there, but you may have to go digging through the columns to see what exists.<\/p>\n

using an xer file viewer<\/a> like schedulereader can be a good choice for auditing specifically what global objects (and the associated values) exist in an .xer file. there are few other tools that can do the same (but please let a comment if you do know of any other tools).<\/p>\n

with a preview of what global data exists, you can now move to the next step – importing.<\/p>\n

choosing what to import<\/h3>\n

many are not aware that you can pick what global data to include when importing a primavera p6 xer file. it’s a old feature built right into the import screens. the key screen is the one called “import options.”<\/p>\n

there’s also a new feature here to discuss that works with .xml files and give you the ability to convert global data to project data during the import.<\/p>\n

i’ll be going into detail on the import options and the control of global data in my next article. stay tuned!<\/p>\n

did you learn something reading this article? drop me a comment and let me know!<\/em><\/p>\n

 <\/p>\n

\"viewing<\/a><\/span>