Baseline Import Options dialog
You use the Baseline Import Options dialog to 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 also use this dialog to specify how to map tasks in the project or baseline that you are importing with tasks in the active project.
The advantages and disadvantages of working with embedded baselines and baselines that are separate files are listed below:
| Type of baseline | Advantages | Disadvantages |
|---|---|---|
| Embedded | Possible to share a project and its baselines by giving people a single file. | The file size of projects is increased as a project's baselines are saved in the same file as the project. This may present problems if you want to email large projects to people - although you can compress ("zip") files before sending them. |
| Separate file | The file size of projects is smaller. | When sharing a project and its baselines, you need to give people the project file and all of the project's baseline files individually, and ensure that they are saved in the same folder structure to enable the project to locate its baselines. |
Do not embed baselines into projects if you work with projects that are located on a network drive, rather than on your local PC, as this can lead to problems if your network connection fails.
If your setup does not allow baselines to be stored externally - for example, if you use Asta Enterprise with a web-based server administration utility - baselines must be embedded, so you do not get a choice of whether or not to embed.
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.
How to access the Baseline Import Options dialog
To access the Baseline Import Options dialog, click Import from within the Baseline/What If Manager dialog and select the project or baseline that you want to import.
Explanation of the fields on the dialog
| Field | Description |
|---|---|
| Embed baseline |
Select this check box to embed the project or baseline you are importing into the active project file, or clear the check box to import the project or baseline as a separate file, with a .PPB file extension.
If you choose to embed the project or baseline, the two radio buttons on the dialog become available.
If your setup does not allow baselines to be stored externally - for example, if you use Asta Enterprise with a web-based server administration utility - baselines must be embedded, so you do not get a choice of whether or not to embed. |
| Match tasks by object ID (default) |
Click this radio button to map tasks in the project or baseline you are importing to those in the active project using the internal identifying number of each object. An object ID is assigned to each object automatically by Asta Powerproject when the object is created.
If you choose to match tasks using internal object IDs, tasks in the project or baseline you are importing are linked to the tasks in the active project that have identical internal object IDs. |
| Match tasks by unique task ID |
Click this radio button to map tasks in the project or baseline you are importing to those in the active project using the unique task ID of each object. You may want to do this if you use unique task IDs to identify objects in your projects.
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.
|
How do I...
... specify whether to embed the project or baseline being imported?
Select the Embed baseline check box to embed the project or baseline you are importing into the active project file, or clear the check box to import the project or baseline as a separate file, with a .PPB file extension.
If your setup does not allow baselines to be stored externally - for example, if you use Asta Enterprise with a web-based server administration utility - baselines must be embedded, so you do not get a choice of whether or not to embed.
... specify how to map tasks in the project or baseline being imported with tasks in the active project?
- Click the Object ID (default) radio button to map tasks in the project or baseline you are importing to those in the active project using the internal identifying number of each object. An object ID is assigned to each object automatically by Asta Powerproject when the object is created.
- Click the Unique task ID radio button to map tasks in the project or baseline you are importing to those in the active project using the unique task ID of each object. You may want to do this if you use unique task IDs to identify objects in your projects.
Importing a project for use as a baseline