TABLE OF CONTENTS

• Introduction
• Schedule Core Fields
• Resource Core Fields
• Activity Core Fields
• Resource Assignment Core Fields
• Successor Core Fields
• Structure Core Fields

Introduction

If you make a Config using a Template with no SchedEx Terms, the "standard" fields of a schedule will automatically be transferred during an upload, according to the new Schedule Data Ontology - SDO.

This article describes the logic by which the Core field name is populated, on upload, from a Formula that resembles the actual source code used. It is applied relative to the various API response fields in a Microsoft Project (.mpp) file, read through the Aspose.Tasks library – Prj = project, Tsk = task, Rsc = resource, Asn = resource assignment (note that the highlighted words correspond with column names in tables below). 

There will be a table for each Planning Object Type (Schedule, Resource, Activity, Resource Assignment, Successor, and Structure).

Microsoft Project is an upload-only (export) connector – it has no download (import) operation, so there is no reverse direction to document.

Note that the Core Fields read from a named Microsoft Project field can be overridden by mappings in Config (ILAP Term → host field).

Microsoft Project has no Profile concept, and every resource assignment is treated as staff time. Successor links between activities are added from the project's task links during export.

Schedule Core Fields

Resource Core Fields

Activity Core Fields

Notes on the activity export:
• Summary tasks are skipped unless the Config is set to include them; the root task is always skipped.
• Only activities that pass the configured Activity Filter are exported.
• Resource assignments are limited to work resources.
• Successor links (to following activities) are added in a second pass from the project's task links.

Resource Assignment Core Fields

Resource Assignments are nested under an Activity.

Successor Core Fields

Successor links (activity links) are read from the project's task links in a second pass. Each link becomes a Successor on the predecessor activity, pointing at the successor activity.

Structure Core Fields

Microsoft Project exports up to two kinds of structure: Outline-Code structures (from the project's outline-code / custom lookup fields) and a WBS structure (the task work-breakdown hierarchy). Each activity is linked during export to the structure elements it belongs to.

Outline-Code Structure

Outline-Code Structure Element (nested under the structure)

WBS Structure

WBS Structure Element (nested under the structure)

When a specific field is configured as the WBS, that outline-code structure is simply re-typed as Wbs instead of producing a separate WBS structure. Each activity is linked to its outline-code element (by the activity's field value) and to its default-WBS element (by the task's WBS code).