Importing a project for use as a baseline

There may be occasions when you want to import a project for use as a baseline. For example, you might book out part of a project, edit it, then import it back into the original project for use as a baseline. There may also be times when you want to import a baseline back into its project, for example, if you accidentally delete a baseline and need to import a backup copy. The project or baseline that you import obviously needs to be a version of the project you are working with - it makes no sense to import a completely different project and attempt to use that as a baseline.

In some circumstances when you import a project or baseline, you can specify whether you want to embed the project or baseline you are importing into the active project file, or whether you want to import it as a separate file. If you choose to embed the project or baseline you are importing, you must specify how to map the tasks in the imported project or baseline with tasks in the active project. This is because when a project or baseline is imported and embedded, its internal object IDs are changed. You can map tasks using internal object IDs - the ID that is assigned to each object automatically by Asta Powerproject when the object is created - or using unique task IDs. The default mapping method is to use internal object IDs, but if you use unique task IDs to identify objects in your projects, you may prefer to map using unique task IDs.

If you choose to map tasks using unique task IDs, tasks in the project or baseline you are importing are linked to the tasks in the active project that have identical unique task IDs. Despite their name, unique task IDs do not have to be unique within a project; this depends on the way in which they are configured in the project. If the mapping process encounters more than one task with the same unique task ID, it examines the parent chart or summary group to identify which one to map; if there are still duplicates - ie if there is more than one task in a chart or summary group with the same unique task ID - the first task from the set of tasks with duplicate IDs is mapped.

If you import an XER file as a baseline, you do not specify how to map tasks in the XER file with tasks in the active project; tasks are always mapped using unique task IDs in this situation.

Once the import is complete, the imported project, baseline or XER file is added to the list of baselines in the Baseline/What If Manager. A graphical indicator - four horizontal grey bars - is displayed in the Name column in the Baseline/What If Manager dialog for any baselines that are embedded. This makes it easy to identify which baselines are embedded and which exist as separate files. Use the Baseline tab on the Format Bar Chart dialog to display the new baseline.

Related Topics:

Creating baselines

Merging new and changed data into existing baselines

Associating different baselines with individual projects

Displaying baseline information in the bar chart

Displaying baseline information in the spreadsheet

Opening a baseline as a separate project

Reverting to a baseline

Deleting baselines

Setting baseline display options

Viewing baseline information

Asta Vision and baselines

Unique task ID numbering