How P6 WBS Structure is represented in uploaded TransferData

Modified on Thu, 6 Nov at 1:26 PM

TABLE OF CONTENTS

Introduction
The content

Introduction

When a P6 schedule is processed by IDE and uploaded to service, it will always contain a representation of its WBS structure.

This document give insight into this content.

The content

    "Structures": [
        {
            "Description": "WBS",
            "Type": 0,
            "StructureElements": [
                {
                    "Description": "Level1",
                    "SimplifiedProperties": {},
                    "Code": "1",
                    "IlapId": "R-a8740afb-518f-42f4-a6fc-2ce99f8bc190",
                    "HostObjectId": "8374-180404",
                    "FieldValues": {}
                },
                {
                    "Description": "Level1.1",
                    "ParentElementIlapId": "R-a8740afb-518f-42f4-a6fc-2ce99f8bc190",
                    "SimplifiedProperties": {},
                    "Code": "1",
                    "IlapId": "R-293262fa-1a39-4cbb-908f-a97e89eae2d3",
                    "HostObjectId": "8374-180405",
                    "FieldValues": {}
                },
                {
                    "Description": "Level2",
                    "SimplifiedProperties": {},
                    "Code": "2",
                    "IlapId": "R-8cab3a39-bae3-4de1-9ecd-72ddc0c16213",
                    "HostObjectId": "8374-180406",
                    "FieldValues": {}
                }
            ],
            "SimplifiedProperties": {},
            "Code": "8374-WBS",
            "IlapId": "R-fcf007b6-b2d8-427c-8112-83b2693c486e",
            "FieldValues": {}
        }
    ],

NOTES:

The "Type" enum (on row 4) have these possible values: 0=Wbs, 1=FlatList, 2=HierarchicalList
The "Code" values for each node is the leaf value, so the full path for a node needs to be deduced.
The code for the structure is derived from this pattern: "<ScheduleObjectId>-WBS" and the description is always "WBS".