Importing from MS Project

An imported plan will vary slightly depending on whether or not the schedule was originally created in NetPoint or MS Project. If the schedule was originally created in NetPoint, subsequently exported, and is now being imported back, the look and layout of the schedule will be the same. If the schedule was created in MS Project, or if it was created in NetPoint using a version prior to 4.1, release 25 Feb 2013, NetPoint will layout the network avoiding clashes, but the user should run the automated layout engine. For more information, see Running the Engine. If further manual repositioning of data elements is desired, see Repositioning Fields (GEM). Instructions are provided below.

Steps

In MS Project

  1. While viewing the desired schedule, click File > Save As from the menu bar.
  2. Click next to Save as type and choose XML Format (*.xml).
  3. If desired, change the File name and click Save.

In NetPoint

  1. Click File > Import/Export from the menu bar and choose Import from MS Project XM.
  2. Browse for the desired XML file and click Open. A report will open showing a summary of any incompatibilities that were found.
  3. When ready, click Finalize Import. The schedule will then open in NetPoint.

NOTE: A non-MS Project-based xml file can technically be chosen but will not properly import.

Notes

Import Report – MS Project

10211-c

Column Definition
Type Type of notification. Info notifications include confirmations and minor incompatibilities, such as when items are converted to be compatible with NetPoint. Warning notifications include major incompatibilities, such as items that are changed, which affect logic, or items not being imported altogether.
Issue A general category for the notification, such as calendars, resources, data dates, etc.
Item Id (NetPoint) The identifier as found in NetPoint.
Item ID (Source) The identifier as found in MS Project.
Item Description The name or description of the item in question.
Message The notification itself.
Resolution How (if possible) the issue has been resolved.

Supported Fields

MS Project Objects and Fields

The following MS Project objects and fields are brought into NetPoint. If a field is not listed, then it does NOT transfer. Some examples of fields that do not transfer are identified where relevant

This field in MSP Becomes this field in NetPoint Notes
Task Activity
Task (with 0 duration) Start/Finish Milestone If the task has no predecessor or starts before noon, it becomes a start milestone. Otherwise, it becomes a finish milestone.
Summary Task Hammock Only one level (the lowest) is brought in.
Lag Embedded node or link lag If positive, the lag will be captured in the embed unless it is larger than the duration of the activity, in which case it will be captured in the link lag. If negative, it will be captured in the link lag for FS relationships, otherwise ignored.
Name Description
NetPoint Activity ID (custom field) ID If the NetPoint Activity ID field isn’t available, then the information in the ID field will transfer over.
Start Start Date
Finish Finish Date
Actual Start Start Date
Actual Finish Finish Date
Duration Duration
Remaining Duration Remaining Duration
Actual Duration Duration
Free Slack Buffer
Slack Total Float
Calendar Calendar Repeating holidays that do not occur within the entire range of the project will transfer as individual holidays to NetPoint.
Must Start On Start benchmark On activities, ignored.
Must Finish On Finish benchmark On activities, ignored.
Start No Earlier Than Start No Earlier Than
Start No Later Than Ignored
Finish No Earlier Than Ignored
Finish No Later Than Finish No Later Than
Resources Resources MS Project only supports units/day; any schedule that was exported from NetPoint and then brought in should be have its resource assignment distributions reviewed. Furthermore, assignments will only be brought in for activities.
Resource Name Name
Std. Rate Cost/Unit
Type Category
Work (also Units) Rate/Day MS Project only supports units/day.
Codes Codes Codes that have been entered in the Custom Fields tab of a task will become project codes in NetPoint. The following fields are imported.
Custom Field Name Name
Value Value
NetPoint Fields

If the schedule was exported from NetPoint already, everything will be brought in EXCEPT for the following:

Characteristic Result
Layouts Gone
Delays Become activities
Shades Gone
Notepads Gone
Link Geometries Become default
Embed Behaviors Become constant
Custom Positioning Becomes default
Resource Limits Gone
Resource Formatting Become default (color, histogram patterns, color intensities)
Page Size Becomes letter
Page Tiling Becomes 1×1
Grid Spacing Becomes default
Canvas Color Becomes default
Calendar Strips Become default
Calendar Sightlines Become default
Text Size Becomes default
Text Objects Gone