Phantom task

[logosmjt]

Problem Description

After a user deletes the task with outline number 1.2.4 (task name "L3 3.4") from the DATA-01_V3 project in MS Project
and uploads the updated .mpp file, the Lambda validation pipeline returns a task with GUID
632496a7-9d7a-f111-bcdc-d5c51bcf0e84 that has a null task name.
This GUID cannot be found in either the MS Project UI or the XML file exported from the same .mpp file. It appears to be
a residual "phantom" record left behind in the .mpp binary format after the task was deleted.

Multiple versions were tested, from 13.12.0 through 16.7.0. All versions produce the same phantom task (UID 167,
GUID 632496a7-9d7a-f111-bcdc-d5c51bcf0e84).

MPXJ parsing results for the outline number 3.1.x region:

UID	GUID	Outline Number	Outline Level	Name
158	a3703b34-8f60-f111-bcdb-d5c51bcf0e84	3.1.1	3	L1 3 1 1
164	6321be4d-9460-f111-bcdb-d5c51bcf0e84	3.1.2	3	L1 3 1 3
167	632496a7-9d7a-f111-bcdc-d5c51bcf0e84	3.1.3	3	null
165	02d6dd4b-b460-f111-bcdb-d5c51bcf0e84	3.1.4	3	L1 3 1 4
168	00c36fd3-2c7f-f111-bcdc-d5c51bcf0e84	3.1.5	3	L1 3 1 5

In MS Project and its XML export, UID 167 does not exist, and UIDs 165 and 168 have outline numbers 3.1.3 and
3.1.4 respectively (not 3.1.4 and 3.1.5 as reported by MPXJ).

DATA-01_V3_phantom_task.mpp.zip

[joniles]

Thanks for opening the issue, I'll take a look as soon as I can.